From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Pavan Deolasee" <pavan(dot)deolasee(at)enterprisedb(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Bug in VACUUM FULL ? |
Date: | 2007-03-14 14:58:41 |
Message-ID: | 22509.1173884321@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Pavan Deolasee" <pavan(dot)deolasee(at)enterprisedb(dot)com> writes:
> If that assumption is true (and it must be true for us to move
> the chain in pieces), doesn't that mean we don't really need to
> move the RECENTLY_DEAD tuples preceding a DEAD tuple ?
As I've already said several times: they are dead, but at least for
VACUUM FULL's purposes it seems unreasonably difficult to determine that
and remove them. The point at which we'd figure this out is after we've
already performed dead-tuple removal (at least for some of the pages
involved). It would make for a significant increase in logical
complexity, and that code is too damn complicated already. Since we
know this is a seldom-seen corner case, I'm not going to risk
introducing new bugs to recycle a few tuples a bit sooner.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2007-03-14 14:59:39 | Re: [PATCHES] Bitmapscan changes |
Previous Message | Andrew Dunstan | 2007-03-14 14:53:31 | Re: Daylight Saving Time question PostgreSQL 8.1.4 |