12 Commits (02490d4692c46bee3e9279e79c5d07c576d2a32c)

Author	SHA1	Message	Date
Tom Lane	15a3fe6d63	Properly mark pg_freespace() function as strict. Also update ... uninstall script to match reality.	17 years ago
Heikki Linnakangas	6736da5484	Make the blkno arguments bigints instead of int4s. A signed int4 is not ... large enough for block numbers higher than 2^31. The old pre-FSM-rewrite pg_freespacemap implementation got this right. While we're at it, remove some unnecessary #includes.	17 years ago
Heikki Linnakangas	d3de08a008	Rewrite pg_freespacemap to match the new FSM implementation. I missed these ... changes from the main FSM commit for some reason.	17 years ago
Heikki Linnakangas	15c121b3ed	Rewrite the FSM. Instead of relying on a fixed-size shared memory segment, the ... free space information is stored in a dedicated FSM relation fork, with each relation (except for hash indexes; they don't use FSM). This eliminates the max_fsm_relations and max_fsm_pages GUC options; remove any trace of them from the backend, initdb, and documentation. Rewrite contrib/pg_freespacemap to match the new FSM implementation. Also introduce a new variant of the get_raw_page(regclass, int4, int4) function in contrib/pageinspect that let's you to return pages from any relation fork, and a new fsm_page_contents() function to inspect the new FSM pages.	17 years ago
Bruce Momjian	33e2e02493	Add CVS version labels to all install/uninstall scripts.	18 years ago
Bruce Momjian	926bbab448	Make /contrib install/uninstall script consistent: ... remove transactions use create or replace function make formatting consistent set search patch on first line Add documentation on modifying *.sql to set the search patch, and mention that major upgrades should still run the installation scripts. Some of these issues were spotted by Tom today.	18 years ago
Tom Lane	9e936693a9	Fix free space map to correctly track the total amount of FSM space needed ... even when a single relation requires more than max_fsm_pages pages. Also, make VACUUM emit a warning in this case, since it likely means that VACUUM FULL or other drastic corrective measure is needed. Per reports from Jeff Frost and others of unexpected changes in the claimed max_fsm_pages need.	20 years ago
Tom Lane	a43974c6ba	Code review for contrib/pg_freespacemap. Add a storedpages column to ... pg_freespacemap_relations --- while one could theoretically get that number by counting rows in pg_freespacemap_pages, it's surely the hard way to do it. Avoid expensive and inconvenient conversion to and from text format. Minor code and docs cleanup.	20 years ago
Bruce Momjian	136bea1540	Split out pg_freespace views to one for relations and another for pages, ... pg_freespacemap_relations and pg_freespacemap_pages. Mark Kirkwood	20 years ago
Bruce Momjian	028ec5cb0f	Adjust /contrib/pg_freespace to show index free space as NULL (FSM only ... tracks index pages, not free space on pages): 1/ Index free bytes set to NULL 2/ Comment added to the README briefly mentioning the index business 3/ Columns reordered more logically 4/ 'Blockid' column removed 5/ Free bytes column renamed to just 'bytes' instead of 'blockfreebytes' Mark Kirkwood	20 years ago
Peter Eisentraut	7f4f42fa10	Clean up CREATE FUNCTION syntax usage in contrib and elsewhere, in ... particular get rid of single quotes around language names and old WITH () construct.	20 years ago
Bruce Momjian	d5dd3d451e	Add contrib/pg_freespacemap to display free space map information. ... Mark Kirkwood	20 years ago