Re: Determine potential change in table size after a column dropped?

From: Thomas Kellerer <shammat(at)gmx(dot)net>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Determine potential change in table size after a column dropped?
Date: 2022-01-24 08:44:12
Message-ID: 171c51df-da5e-d788-e051-8d5c53cf754b@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Laurenz Albe schrieb am 24.01.2022 um 09:28:
> On Sat, 2022-01-22 at 09:08 -0800, Wells Oliver wrote:
>> I need only drop the column and VACUUM FULL the table, and not the entire DB, right?
>
> Not that VACUUM (FULL) will *not* physically get rid of a dropped column,
> as it just copies the complete rows to a new table.

I always wondered why that is the case.

If the table is rewritten entirely, wouldn't that also be an option to
really get rid of dropped columns?

Is there a technical reason, or just a case of "no one cared enough to change it"?

Regards
Thomas

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Wells Oliver 2022-01-24 16:08:10 Re: Determine potential change in table size after a column dropped?
Previous Message Laurenz Albe 2022-01-24 08:28:44 Re: Determine potential change in table size after a column dropped?