Re: Re: reloption to prevent VACUUM from truncating empty pages atthe end of relation - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Re: reloption to prevent VACUUM from truncating empty pages atthe end of relation
Date
Msg-id CA+Tgmoas0L1S4MMWpNZzz_kaffPF=iEtAn0KNLuvkUE43S2ZAw@mail.gmail.com
Whole thread Raw
In response to Re: Re: reloption to prevent VACUUM from truncating empty pages atthe end of relation  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: Re: reloption to prevent VACUUM from truncating empty pages atthe end of relation  (Julien Rouhaud <rjuju123@gmail.com>)
Re: Re: reloption to prevent VACUUM from truncating empty pages atthe end of relation  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Thu, Apr 4, 2019 at 9:19 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
> As INDEX_CLEANUP option has been added by commit a96c41f, the new
> option for this feature could also accept zero or one boolean
> argument, that is SHRINK_TABLE [true|false] and true by default.
> Explicit options on VACUUM command overwrite options set by
> reloptions. And if the boolean argument is omitted the option depends
> on the reloptions.

Yes, I think that's how it should work, because that's how the other
option works, and there's no compelling reason to be consistent.

My preference is for "truncate" over "shrink".

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Changes to pg_dump/psql following collation "C" in the catalog
Next
From: Andres Freund
Date:
Subject: Re: Small typo fix on tableam documentation