| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, 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-17 19:12:26 |
| Message-ID: | 20180417191226.vim4kk6n52tlt47a@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018-04-17 15:09:18 -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> > Andres was working on a radix tree structure to fix this problem, but
> > that seems to be abandoned now, and it seems a major undertaking.
I hope to re-ignite work on that later in the v12 cycle. But
realistically that means it's not going to be mergable for v12.
> > While I agree that the proposed solution is a wart, it seems much
> > better than no solution at all. Can we consider Fujii's proposal as
> > a temporary measure until we fix shared buffers? I'm +1 on it
> > myself.
>
> Once we've introduced a user-visible reloption it's going to be
> practically impossible to get rid of it, so I'm -1.
It's not much work to maintain though? And even the brief AEL lock can
cause troubles, leaving the scan aside. So I'm like +0.1 or such.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-04-17 19:26:49 | Re: pgsql: Support partition pruning at execution time |
| Previous Message | Tom Lane | 2018-04-17 19:09:18 | Re: reloption to prevent VACUUM from truncating empty pages at the end of relation |