postgres

History

Tom Lane 32ea236361 Improve the IndexVacuumInfo/IndexBulkDeleteResult API to allow somewhat sane behavior in cases where we don't know the heap tuple count accurately; in particular partial vacuum, but this also makes the API a bit more useful for ANALYZE. This patch adds "estimated_count" flags to both structs so that an approximate count can be flagged as such, and adjusts the logic so that approximate counts are not used for updating pg_class.reltuples. This fixes my previous complaint that VACUUM was putting ridiculous values into pg_class.reltuples for indexes. The actual impact of that bug is limited, because the planner only pays attention to reltuples for an index if the index is partial; which probably explains why beta testers hadn't noticed a degradation in plan quality from it. But it needs to be fixed. The whole thing is a bit messy and should be redesigned in future, because reltuples now has the potential to drift quite far away from reality when a long period elapses with no non-partial vacuums. But this is as good as it's going to get for 8.4.		17 years ago
..
common	Use more-portable coding for the check on handing out the last available	17 years ago
gin	Improve the IndexVacuumInfo/IndexBulkDeleteResult API to allow somewhat sane	17 years ago
gist	Improve the IndexVacuumInfo/IndexBulkDeleteResult API to allow somewhat sane	17 years ago
hash	Improve the IndexVacuumInfo/IndexBulkDeleteResult API to allow somewhat sane	17 years ago
heap	Fix LOCK TABLE to eliminate the race condition that could make it give weird	17 years ago
index	Implement "fastupdate" support for GIN indexes, in which we try to accumulate	17 years ago
nbtree	Improve the IndexVacuumInfo/IndexBulkDeleteResult API to allow somewhat sane	17 years ago
transam	Only recycle normal files in pg_xlog as WAL segments. pg_standby creates	17 years ago
Makefile	Refactor backend makefiles to remove lots of duplicate code	18 years ago