Re: Problem with TOAST tables when removing TOASTable column

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

=?iso-8859-2?Q?Wojciech_Strza=B3ka?= <wstrzalka(at)gmail(dot)com> writes:
> In my opinion the fact that dropping column doesn't release it's toastable resources is a bug.

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.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Wojciech Strzałka 2008-05-14 15:21:05 Re: Problem with TOAST tables when removing TOASTable column
Previous Message Wojciech Strzałka 2008-05-14 14:45:53 Problem with TOAST tables when removing TOASTable column