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

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: reloption to prevent VACUUM from truncating empty pages at the end of relation
Date: 2018-04-19 19:56:59
Message-ID: 20180419195659.btda3ngcqj7eb4lz@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Paquier wrote:

> Then, let's consider the beginning of the first commit fest of v12 as
> judgement. Implementing radix tree for shared buffers is a long-term
> project, which has no guarantee to get merged, while a visibly-simple
> reloptions which helps in some cases...

In the scenario we studied, the truncations were causing periodic
hiccups which were quite severe. The truncations were completely
useless anyway because the table grew back to the original size daily (a
few dozen GBs I think). That was a lot of unnecessary work, and under
exclusive lock no less.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-04-19 19:59:44 Re: initdb fails to initialize data directory
Previous Message Christopher Browne 2018-04-19 19:55:40 Re: Built-in connection pooling