Re: why there is not VACUUM FULL CONCURRENTLY? - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: why there is not VACUUM FULL CONCURRENTLY?
Date
Msg-id Z6Emm1Sj8Xz1hoFO@nathan
Whole thread Raw
In response to Re: why there is not VACUUM FULL CONCURRENTLY?  (Michael Banck <mbanck@gmx.net>)
List pgsql-hackers
On Thu, Jan 30, 2025 at 04:29:35PM +0100, Alvaro Herrera wrote:
> A bunch of people discussed this patch in today's developer meeting in
> Brussels.  There's pretty much a consensus on using the verb REPACK
> CONCURRENTLY for this new command -- where unadorned REPACK would be
> VACUUM FULL, and we'd have something like REPACK WITH INDEX or maybe
> REPACK USING INDEX to take the CLUSTER place.

+1

One small thing I thought of after the meeting was that this effectively
forces users to always specify an index if they want to REPACK WITH INDEX.
Today, CLUSTER will use the same index as before if one is not specified.
IMHO requiring users to specify the index is entirely reasonable, but I
figured I'd at least note the behavior change.

-- 
nathan



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Better title output for psql \dt \di etc. commands
Next
From: Sami Imseih
Date:
Subject: Re: improve DEBUG1 logging of parallel workers for CREATE INDEX?