Re: why there is not VACUUM FULL CONCURRENTLY?

Antonin Houska <ah@cybertec.at>

From: Antonin Houska <ah@cybertec.at>

To: jian he <jian.universality@gmail.com>

Cc: Matheus Alcantara <matheusssilv97@gmail.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Marcos Pegoraro <marcos@f10.com.br>, Michael Banck <mbanck@gmx.net>, Junwang Zhao <zhjwpku@gmail.com>, Kirill Reshke <reshkekirill@gmail.com>, Pavel Stehule <pavel.stehule@gmail.com>, Michael Paquier <michael@paquier.xyz>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2025-06-09T10:19:15Z

Lists: pgsql-hackers

Attachments

v14-0001-Add-REPACK-command.patch (text/x-diff)

jian he <jian.universality@gmail.com> wrote:

> On Fri, Apr 11, 2025 at 5:28 PM Antonin Houska <ah@cybertec.at> wrote:
> >
> > Please check the next version [1]. Thanks for your input.
> >
> > [1] https://www.postgresql.org/message-id/97795.1744363522%40localhost
> >
> 
> Hi, I’ve briefly experimented with v13-0001.

Thanks! v14 addresses your comments.

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

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