Re: First-draft release notes for next week's releases

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: First-draft release notes for next week's releases
Date: 2014-03-17 23:58:18
Message-ID: 11889.1395100698@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Andres Freund wrote:
>> I think the best way to really cleanup a table is to use something like:
>> ALTER TABLE rew ALTER COLUMN data TYPE text USING (data);
>> where text is the previous type of the column. That should trigger a
>> full table rewrite, without any finesse about tracking ctid chains.

> Isn't this what VACUUM FULL does?

AFAIR, both VACUUM FULL and CLUSTER will attempt to preserve update
chains, and thus will probably get confused by this bug (though I've
not looked into exactly what will happen). I'm not real sure that ALTER
TABLE is any better --- doesn't all that stuff go through rewriteheap.c
now?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-03-18 00:01:00 Re: First-draft release notes for next week's releases
Previous Message Andres Freund 2014-03-17 23:56:42 Re: First-draft release notes for next week's releases