Re: PostgreSQL Limits and lack of documentation about them. - Mailing list pgsql-hackers

From David Rowley
Subject Re: PostgreSQL Limits and lack of documentation about them.
Date
Msg-id CAKJS1f8CukW7407P-QiB4cCfi6GrpJC6VAHDuHxGtaHbQi_SVw@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL Limits and lack of documentation about them.  (Steve Crawford <scrawford@pinpointresearch.com>)
Responses Re: PostgreSQL Limits and lack of documentation about them.  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Thu, 29 Nov 2018 at 08:17, Steve Crawford
<scrawford@pinpointresearch.com> wrote:
> Both for my edification and as a potentially important documentation detail, do operations that rebuild the table
suchas CLUSTER or pg_repack reclaim the column space?
 

I've never used pg_repack, but CLUSTER will reform the tuples so that
they no longer store the actual value for the Datums belonging to the
dropped column. They'll still contain the null bitmap to mention that
the dropped column's value is NULL.  The row won't disappear from
pg_attribute, so the attnums are not resequenced, therefore we must
maintain the dropped column with the NULL marking.

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: PostgreSQL Limits and lack of documentation about them.
Next
From: Tomas Vondra
Date:
Subject: Re: COPY FROM WHEN condition