9 Commits (473af3973710b9e2f4e945d8290adae8de9696cc)

Author	SHA1	Message	Date
Bruce Momjian	65e806cba1	pgindent run for 9.0	16 years ago
Tom Lane	cbe9d6beb4	Fix up rickety handling of relation-truncation interlocks. ... Move rd_targblock, rd_fsm_nblocks, and rd_vm_nblocks from relcache to the smgr relation entries, so that they will get reset to InvalidBlockNumber whenever an smgr-level flush happens. Because we now send smgr invalidation messages immediately (not at end of transaction) when a relation truncation occurs, this ensures that other backends will reset their values before they next access the relation. We no longer need the unreliable assumption that a VACUUM that's doing a truncation will hold its AccessExclusive lock until commit --- in fact, we can intentionally release that lock as soon as we've completed the truncation. This patch therefore reverts (most of) Alvaro's patch of 2009-11-10, as well as my marginal hacking on it yesterday. We can also get rid of assorted no-longer-needed relcache flushes, which are far more expensive than an smgr flush because they kill a lot more state. In passing this patch fixes smgr_redo's failure to perform visibility-map truncation, and cleans up some rather dubious assumptions in freespace.c and visibilitymap.c about when rd_fsm_nblocks and rd_vm_nblocks can be out of date.	16 years ago
Bruce Momjian	0239800893	Update copyright for the year 2010.	16 years ago
Tom Lane	7fc7a7c4d0	Fix a violation of WAL coding rules in the recent patch to include an ... "all tuples visible" flag in heap page headers. The flag update *must* be applied before calling XLogInsert, but heap_update and the tuple moving routines in VACUUM FULL were ignoring this rule. A crash and replay could therefore leave the flag incorrectly set, causing rows to appear visible in seqscans when they should not be. This might explain recent reports of data corruption from Jeff Ross and others. In passing, do a bit of editorialization on comments in visibilitymap.c.	16 years ago
Heikki Linnakangas	efa8544fd5	Fix a few errors in comments. Patch by Fujii Masao, plus the one in ... visibilitymap.c by me.	16 years ago
Bruce Momjian	d747140279	8.4 pgindent run, with new combined Linux/FreeBSD/MinGW typedef list ... provided by Andrew.	16 years ago
Bruce Momjian	511db38ace	Update copyright for 2009.	17 years ago
Heikki Linnakangas	7a567d9407	MAPSIZE macro needs to use MAXALIGN(SizeOfPageHeaderData) instead of ... SizeOfPageHeaderData, like PageGetContents does. Per report by Pavan Deolasee.	17 years ago
Heikki Linnakangas	608195a3a3	Introduce visibility map. The visibility map is a bitmap with one bit per ... heap page, where a set bit indicates that all tuples on the page are visible to all transactions, and the page therefore doesn't need vacuuming. It is stored in a new relation fork. Lazy vacuum uses the visibility map to skip pages that don't need vacuuming. Vacuum is also responsible for setting the bits in the map. In the future, this can hopefully be used to implement index-only-scans, but we can't currently guarantee that the visibility map is always 100% up-to-date. In addition to the visibility map, there's a new PD_ALL_VISIBLE flag on each heap page, also indicating that all tuples on the page are visible to all transactions. It's important that this flag is kept up-to-date. It is also used to skip visibility tests in sequential scans, which gives a small performance gain on seqscans.	17 years ago