postgres

Author	SHA1	Message	Date
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
Bruce Momjian	d5dd3d451e	Add contrib/pg_freespacemap to display free space map information. Mark Kirkwood	20 years ago