|From:||"Jamison, Kirk" <k(dot)jamison(at)jp(dot)fujitsu(dot)com>|
|To:||"Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>|
|Cc:||Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 'Amit Kapila' <amit(dot)kapila16(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||RE: reloption to prevent VACUUM from truncating empty pages at the end of relation|
|Views:||Raw Message | Whole Thread | Download mbox|
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.
Thank you for this.
I applied the patch. It builds successfully, and passed the regression tests.
I also tried testing with the parameter when its enabled and disabled,
and it works as intended for CREATE TABLE and ALTER TABLE a SET (shrink_enabled = on/off) and RESET (shrink_enabled).
I have yet to test the performance benchmark.
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 think if most seem to agree to have this solution in place
and to review this further and cover what might be missing,
then shall we register this to next CF?
|Next Message||Tsunakawa, Takayuki||2019-02-01 07:08:28||RE: reloption to prevent VACUUM from truncating empty pages at the end of relation|
|Previous Message||Haribabu Kommi||2019-02-01 06:34:05||initdb --allow-group-access behaviour in windows|