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

From Julien Rouhaud
Subject Re: Re: reloption to prevent VACUUM from truncating empty pages atthe end of relation
Date
Msg-id CAOBaU_a6fQ67piWOCszMG3036CrJE9FEr8j3JeDeqxCr1n2EGA@mail.gmail.com
Whole thread Raw
In response to Re: Re: reloption to prevent VACUUM from truncating empty pages atthe end of relation  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Re: reloption to prevent VACUUM from truncating empty pages atthe end of relation  (Robert Haas <robertmhaas@gmail.com>)
Re: Re: reloption to prevent VACUUM from truncating empty pages at the end of relation  (Adrien Mobile <adrien.nayrat@anayrat.info>)
List pgsql-hackers
On Fri, Apr 5, 2019 at 7:04 PM Robert Haas <robertmhaas@gmail.com> wrote:
>
> 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.

Indeed, I totally agree.

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

I don't really like "shrink" either, but users already have problems
to get the difference between VACUUM and VACUUM FULL, I'm afraid that
"VACUUM TRUNCATE_TABLE" will just make things worse.



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [PROPOSAL] Shared Ispell dictionaries
Next
From: Robert Haas
Date:
Subject: Re: Re: reloption to prevent VACUUM from truncating empty pages atthe end of relation