From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, 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 20:06:45 |
Message-ID: | CAFj8pRBE22MBbaMbP1yqmwNRq4SVBRXhoP1EDaLqG5FsvKM2pw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2018-04-19 21:56 GMT+02:00 Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>:
> 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.
>
has sense
Pavel
>
> --
> Álvaro Herrera https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2018-04-19 20:23:58 | Re: reloption to prevent VACUUM from truncating empty pages at the end of relation |
Previous Message | Alvaro Herrera | 2018-04-19 19:59:44 | Re: initdb fails to initialize data directory |