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

From Antonin Houska
Subject Re: A concurrent VACUUM FULL?
Date
Msg-id 18940.1751277822@localhost
Whole thread Raw
In response to A concurrent VACUUM FULL?  (Erik Nordström <erik@timescale.com>)
Responses Re: A concurrent VACUUM FULL?
List pgsql-hackers
Erik Nordström <erik@timescale.com> wrote:

> Hi hackers,
>
> I've been looking at the code for CLUSTER/VACUUM FULL, and whether it is possible to do a concurrent version of it
usinga 
> multi-transactional approach similar to concurrent reindexing and partition detach.
>
> The idea would be to hold weaker locks in TX1 when doing the heap rewrite (essentially allow reads but prevent
writes),and then do the 
> actual heap swap in a second TX2 transaction.

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.)

--
Antonin Houska
Web: https://www.cybertec-postgresql.com

[1] https://commitfest.postgresql.org/patch/5117/



pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Report bytes and transactions actually sent downtream
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] Remove unused #include's in src/backend/utils/adt/*