Re: VACUUM FULL vs dropped columns - Mailing list pgsql-hackers

From Tom Lane
Subject Re: VACUUM FULL vs dropped columns
Date
Msg-id 18375.1520723971@sss.pgh.pa.us
Whole thread Raw
In response to VACUUM FULL vs dropped columns  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: VACUUM FULL vs dropped columns  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List pgsql-hackers
Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
> Why does VACUUM FULL cause the size of this table with a single
> dropped column (1 out of 1000) cause the table size to double?

VACUUM FULL will rewrite the tuples with a null bitmap where they
had none before (cf reform_and_rewrite_tuple).  That's only a rather
marginal increase in the tuple size, but in this particular example,
it pushes the tuples from just under half a page to just over, so
that you go from 2 tuples/page to 1.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Parallel Aggregates for string_agg and array_agg
Next
From: Andrew Dunstan
Date:
Subject: Re: VACUUM FULL vs dropped columns