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

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "Alvaro Herrera" <alvherre(at)atentus(dot)com>, <pgsql-committers(at)postgresql(dot)org>
Subject: TOAST & DROP COLUMN (Was: RE: pgsql-server/ oc/src/sgml/ref/cluster.sgml rc/ ... )
Date: 2002-08-12 02:17:18
Message-ID: GNELIHDDFBOCMGBFGEFOGEKACDAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2002-08-12 02:25:18 Re: [SECURITY] DoS attack on backend possible (was: Re:
Previous Message Tom Lane 2002-08-12 00:36:12 pgsql-server/ oc/src/sgml/runtime.sgml rc/back ...