On Wed, Dec 17, 2008 at 3:29 PM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote: > > > I don't quite understand this paragraph. If there's any DEAD tuples or > line-pointers, the all-visible flag can't be set. After an UPDATE or DELETE, > it indeed takes two vacuums until the bits in the visibility map are set. > > Or did you mean that it only works because the prune phase sets the hint > bits on the tuples? HeapTupleSatisfiesVacuum sets them too, so we're not > relying on the prune phase to set them. >
No, I am saying, HOT-prune removes all DEAD tuples from the page (not the DEAD line pointers though) and that's why you may not need two vacuums for the visibility bit to set because the first phase of vacuum would not find any DEAD tuples. Without HOT prune, two vacuums will be required to set the bit and that would be counter intuitive because somebody who has just run vacuum on the table would expect the next vacuum to be no-op if there are no updates/deletes in between. Thanks, Pavan -- Pavan Deolasee EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
