TOAST & DROP COLUMN (Was: RE: pgsql-server/ oc/src/sgml/ref/cluster.sgml rc/ ... ) - Mailing list pgsql-committers

From Christopher Kings-Lynne
Subject TOAST & DROP COLUMN (Was: RE: pgsql-server/ oc/src/sgml/ref/cluster.sgml rc/ ... )
Date
Msg-id GNELIHDDFBOCMGBFGEFOGEKACDAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to Re: pgsql-server/ oc/src/sgml/ref/cluster.sgml rc/ ...  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: TOAST & DROP COLUMN (Was: RE: pgsql-server/ oc/src/sgml/ref/cluster.sgml rc/ ... )
List pgsql-committers
> I was too tired last night to really think about this.  What I had in
> mind when I wrote the above was to somehow disable the TOAST machinery
> while copying tuples, so that any toasted values in the new heap would
> still reference the old toast table.  That would avoid "unnecessary"
> copying of the toasted datums ... but it looks ugly to do.

Incidentally - will a dropped column definitely have its TOAST data
reclaimed when you do the "update set col=col;" ?

Chris


pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql-server/ oc/src/sgml/runtime.sgml rc/back ...
Next
From: Tom Lane
Date:
Subject: Re: TOAST & DROP COLUMN (Was: RE: pgsql-server/ oc/src/sgml/ref/cluster.sgml rc/ ... )