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

From Fujii Masao
Subject Re: Re: reloption to prevent VACUUM from truncating empty pages atthe end of relation
Date
Msg-id CAHGQGwFAjm3FkU1G_2AVTUOSb0Y1EfJNnXAd9sJhCvSWOCvcjA@mail.gmail.com
Whole thread Raw
In response to RE: Re: reloption to prevent VACUUM from truncating empty pages atthe end 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 Thu, Mar 28, 2019 at 11:45 AM Tsunakawa, Takayuki
<tsunakawa.takay@jp.fujitsu.com> wrote:
>
> From: Robert Haas [mailto:robertmhaas@gmail.com]
> > 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.
>
> Yeah, I have the same feeling.  OTOH, as I referred in this thread, shrink is used instead of truncate in the
PostgreSQLdocumentation.  So, I chose shrink.  To repeat myself, I'm comfortable with either word.  I'd like the
committerto choose what he thinks better. 

+      This parameter cannot be set for TOAST tables.

reloption for TOAST is also required?

Regards,

--
Fujii Masao



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: partitioned tables referenced by FKs
Next
From: Pavel Stehule
Date:
Subject: Re: ToDo: show size of partitioned table