Re: Problem with TOAST tables when removing TOASTable column

From: Wojciech Strzałka <wstrzalka(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Problem with TOAST tables when removing TOASTable column
Date: 2008-05-14 15:21:05
Message-ID: 323199382.20080514172105@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


> 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?

Wojtek Strzalka

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2008-05-14 15:34:49 Re: BUG #4167: When generating UUID using UUID-OSSP module, UUIDs are not unique on Windows
Previous Message Tom Lane 2008-05-14 15:11:21 Re: Problem with TOAST tables when removing TOASTable column