Postgres Pro
Downloads
Home   >   mailing lists

Re: Determine potential change in table size after a column dropped? - Mailing list pgsql-admin

From Thomas Kellerer
Subject Re: Determine potential change in table size after a column dropped?
Date
Msg-id 171c51df-da5e-d788-e051-8d5c53cf754b@gmx.net
Whole thread Raw
In response to Re: Determine potential change in table size after a column dropped?  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-admin
Tree view 
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

pgsql-admin by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Determine potential change in table size after a column dropped?
Next
From: Wells Oliver
Date:
Subject: Re: Determine potential change in table size after a column dropped?