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+TgmoZ6=1nqsE_hqfBqGFNedPkTV-VqL5gw9Jz6ivogBgTQxg@mail.gmail.com
Whole thread Raw
In response to RE: reloption to prevent VACUUM from truncating empty pages at theend of relation  ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>)
Responses RE: Re: reloption to prevent VACUUM from truncating empty pages atthe end of relation
List pgsql-hackers
On Tue, Mar 26, 2019 at 10:35 PM Tsunakawa, Takayuki
<tsunakawa.takay@jp.fujitsu.com> wrote:
> I almost have the same view as Sawada-san.  The reloption vacuum_shrink_enabled is a positive name and follows the
namingstyle of other reloptions.  I hope this matches the style you have in mind.
 

You're both right and I'm wrong.

However, I think it would be better to stick with the term 'truncate'
which is widely-used already, rather than introducing a new term.

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



pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: Planning counters in pg_stat_statements (using pgss_store)
Next
From: Peter Eisentraut
Date:
Subject: Re: Should the docs have a warning about pg_stat_reset()?