Postgres Pro
Downloads
Home   >   mailing lists

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

From Julien Rouhaud
Subject Re: reloption to prevent VACUUM from truncating empty pages at theend of relation
Date
Msg-id CAOBaU_bb23Y0hZyJUuH9vvZmr4JZ=dbY3jyLCT==a3orcCRX9Q@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: reloption to prevent VACUUM from truncating empty pages at theend of relation  ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>)
List pgsql-hackers
Tree view 
On Fri, Feb 22, 2019 at 3:39 AM Tsunakawa, Takayuki
<tsunakawa.takay@jp.fujitsu.com> wrote:
>
> No, changing the parameter acquires ShareUpdaeExclusive lock.  I just imitated the description for n_distinct in the
samecomment block.  The meaning is that the setting cannot be changed during VACUUM, so in-flight VACUUM is not
affected.

Ah I see, thanks!  I find this a little bit confusing but if that's
already documented like this for other parameters then I guess that's
ok.

One last thing, I think we should at least add one regression test for
this setting.  The one you provided previously seems perfectly suited.

pgsql-hackers by date:

Previous
From: Antonin Houska
Date:
Subject: Re: Unnecessary checks for new rows by some RI trigger functions?
Next
From: "Matsumura, Ryo"
Date:
Subject: RE: SQL statement PREPARE does not work in ECPG