Re: Problem with TOAST tables when removing TOASTable column - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Problem with TOAST tables when removing TOASTable column
Date
Msg-id 20859.1210782149@sss.pgh.pa.us
Whole thread Raw
In response to Re: Problem with TOAST tables when removing TOASTable column  (Wojciech Strzałka <wstrzalka@gmail.com>)
List pgsql-bugs
Wojciech Strzałka <wstrzalka@gmail.com> writes:
>> To make that happen would require (at least) a full table scan.  I think
>> most people are more interested in DROP COLUMN being a cheap operation
>> than in having the space be reclaimed quickly.

>> For a comparison point: large field values that don't happen to get
>> toasted don't vanish immediately, either.

> I agree DROP COLUMN should be cheap and I don't really expect it to happend immediately,
> but shouldn't VACUUM FULL clean it up?

No, changing the content of existing tuples is outside VACUUM's purview.

FWIW, I believe that a CLUSTER would clean it up, and would likely be
faster than a VACUUM FULL anyway.
        regards, tom lane


pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #4167: When generating UUID using UUID-OSSP module, UUIDs are not unique on Windows
Next
From: "Francisco Leovey"
Date:
Subject: BUG #4168: ECPG refuses datestyle SQL