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

From Laurenz Albe
Subject Re: reloption to prevent VACUUM from truncating empty pages at theend of relation
Date
Msg-id a6f65913f2be581d31c5845202d224011dc6fc1e.camel@cybertec.at
Whole thread Raw
In response to RE: reloption to prevent VACUUM from truncating empty pages at theend of relation  ("Jamison, Kirk" <k.jamison@jp.fujitsu.com>)
Responses Re: reloption to prevent VACUUM from truncating empty pages at theend of relation  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Jamison, Kirk wrote:
> On February 1, 2019, Tsunakawa, Takayuki wrote: 
> 
> > > As most people seem to agree adding the reloption, here's the patch.  
> > > It passes make check, and works like this:
> > Sorry, I forgot to include the modified header file.  Revised patch attached.
> 
> I wonder if there is a better reloption name for shrink_enabled. (truncate_enabled, vacuum_enabled? Hmm. No?)
> On the other hand, shrink_enabled seems to describe well what it's supposed to do when vacuuming tables.
> Besides there's a similarly-named autovacuum_enabled option.

I like "shrink_enabled".

It may sound weird in the ears of PostgreSQL hackers, but will make sense to users.

Perhaps "vacuum_shrink_enabled" would be even better.

Yours,
Laurenz Albe



pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: LD_LIBRARY_PATH_RPATH
Next
From: Michael Paquier
Date:
Subject: Re: initdb --allow-group-access behaviour in windows