From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | 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:09:18 |
Message-ID: | 3073.1523992158@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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. 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. I'd much rather
see somebody put some effort into the radix-tree idea than introduce
a kluge that we'll be stuck with, and that doesn't even provide a
good user experience. Disabling vacuum truncation is *not* something
that I think we should recommend.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2018-04-17 19:12:26 | Re: reloption to prevent VACUUM from truncating empty pages at the end of relation |
Previous Message | Alvaro Herrera | 2018-04-17 18:18:36 | Re: reloption to prevent VACUUM from truncating empty pages at the end of relation |