From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: do only critical work during single-user vacuum? |
Date: | 2022-03-31 09:51:05 |
Message-ID: | CAFBsxsHbn4atCHRFXtKQs4FWUhaErdvXa1fX_nouq70pUiC8tw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Mar 16, 2022 at 4:48 AM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>
> On Wed, Feb 16, 2022 at 12:43 AM John Naylor
> <john(dot)naylor(at)enterprisedb(dot)com> wrote:
> > I'll put some effort in finding any way that it might not be robust.
> > After that, changing the message and docs is trivial.
>
> It would be great to be able to totally drop the idea of using
> single-user mode before Postgres 15 feature freeze. How's that going?
Unfortunately, I was distracted from this work for a time, and just as
I had intended to focus on it during March, I was out sick for 2-3
weeks. I gather from subsequent discussion that a full solution goes
beyond just a new warning message and documentation. Either way I'm
not quite prepared to address this in time for v15.
> I suggest that we apply the following patch as part of that work. It
> adds one last final failsafe check at the point that VACUUM makes a
> final decision on rel truncation.
That is one thing that was in the back of my mind, and it seems
reasonable to me.
--
John Naylor
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2022-03-31 09:56:09 | Re: generic plans and "initial" pruning |
Previous Message | Thomas Munro | 2022-03-31 09:49:32 | Re: WIP: WAL prefetch (another approach) |