Re: A concurrent VACUUM FULL? - Mailing list pgsql-hackers

From Álvaro Herrera
Subject Re: A concurrent VACUUM FULL?
Date
Msg-id 202506301146.zotpzfyyxncq@alvherre.pgsql
Whole thread Raw
In response to Re: A concurrent VACUUM FULL?  (Erik Nordström <erik@timescale.com>)
Responses Re: A concurrent VACUUM FULL?
List pgsql-hackers
On 2025-Jun-30, Erik Nordström wrote:

> On Mon, Jun 30, 2025 at 12:03 PM Antonin Houska <ah@cybertec.at> wrote:

> > Patch [1] is in the queue that allows both reads and writes. (An exclusive
> > lock is acquired here for the swaps, but that should be held for very short
> > time.)
>
> That sounds great. Do you know if there's anything I can do to help?

It would be very valuable if you can review the code, test it under the
weirdest conditions you can imagine or just under normal conditions,
proof-read the documentation, try to see if anything is missing that
should be there, and so on.  Everything that you would expect from a new
feature released as part of the next Postgres release.  Any
problems/crashes/ abnormalities that you report before the patch is
included in Postgres, is one less issue that we'll have to deal with
after the release.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"El miedo atento y previsor es la madre de la seguridad" (E. Burke)



pgsql-hackers by date:

Previous
From: Daniil Davydov
Date:
Subject: Re: Prevent internal error at concurrent CREATE OR REPLACE FUNCTION
Next
From: Amit Kapila
Date:
Subject: Re: Report replica identity in pg_publication_tables