Re: "Healing" a table after massive updates

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, "Bill Moran" <wmoran(at)collaborativefusion(dot)com>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Gauthier\, Dave" <dave(dot)gauthier(at)intel(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: "Healing" a table after massive updates
Date: 2008-09-13 16:15:45
Message-ID: 9902.1221322545@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> Incidentally the visibility bugs are indeed entirely fixed in 8.3. In 8.2 and
> before cluster and alter table rewrites can both cause tuples to not appear
> for transactions which were started before the cluster or alter table such as
> a long-running pg_dump.

AFAIK that's true only for CLUSTER, not ALTER TABLE. There would be a
bunch of logical inconsistencies in altering rows and then pretending
you hadn't.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Gregory Stark 2008-09-13 16:50:52 Re: "Healing" a table after massive updates
Previous Message Tom Lane 2008-09-13 16:12:21 Re: Possible limit on transaction size?