Re: why there is not VACUUM FULL CONCURRENTLY?

Michael Banck <mbanck@gmx.net>

From: Michael Banck <mbanck@gmx.net>

To: Kirill Reshke <reshkekirill@gmail.com>

Cc: Antonin Houska <ah@cybertec.at>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Pavel Stehule <pavel.stehule@gmail.com>, Michael Paquier <michael@paquier.xyz>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2024-07-22T09:53:58Z

Lists: pgsql-hackers

On Mon, Jul 22, 2024 at 01:23:03PM +0500, Kirill Reshke wrote:
> Also, should we create a cf entry for this thread already?

I was wondering about this as well, but there is one for the upcoming
commitfest already:

https://commitfest.postgresql.org/49/5117/


Michael

Commits

Add CONCURRENTLY option to REPACK
- 28d534e2ae0a 19 (unreleased) landed
Introduce the REPACK command
- ac58465e0618 19 (unreleased) landed
Adjust signature of cluster_rel() and its subroutines
- cc811f92bac5 18.0 landed
Simplify signature of RewriteTable
- ebd8fc7e47fd 18.0 cited