Horton

Re: Re: reloption to prevent VACUUM from truncating empty pages at the end of relation

David Steele <david@pgmasters.net>

View thread
From: David Steele <david@pgmasters.net>
To: "Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>, Andres Freund <andres@anarazel.de>, "Bossart, Nathan" <bossartn@amazon.com>, Tom Lane <tgl@sss.pgh.pa.us>, Andrew Dunstan <andrew.dunstan@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, Alvaro Herrera <alvherre@2ndquadrant.com>, Michael Paquier <michael@paquier.xyz>, Julien Rouhaud <rjuju123@gmail.com>, Laurenz Albe <laurenz.albe@cybertec.at>, "Jamison, Kirk" <k.jamison@jp.fujitsu.com>, Amit Kapila <amit.kapila16@gmail.com>, Fujii Masao <masao.fujii@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-03-25T08:44:23Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add TRUNCATE parameter to VACUUM.

  2. Add vacuum_truncate reloption.

  3. Allow VACUUM to be run with index cleanup disabled.

On 3/5/19 6:41 AM, Masahiko Sawada wrote:
> 
> I understood the use case. I'm inclined to add DISABLE_INDEX_CLEANUP
> as a reloption.
> 
> It's an improvement but it seems to me that the specifying a threshold
> or scale factor would be more useful for that case than just turning
> on and off. It's something like autovaucum_index_vacuum_scale_factor,
> 0 by default means always trigger index vacuuming and -1 means never
> trigger.

This patch appears to have been stalled for a while.

Takayuki -- the ball appears to be in your court.  Perhaps it would be 
helpful to summarize what you think are next steps?

Regards,
-- 
-David
david@pgmasters.net