Re: why there is not VACUUM FULL CONCURRENTLY?

From: Antonin Houska <ah(at)cybertec(dot)at>
To: jian he <jian(dot)universality(at)gmail(dot)com>
Cc: Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>, Michael Banck <mbanck(at)gmx(dot)net>, Junwang Zhao <zhjwpku(at)gmail(dot)com>, Kirill Reshke <reshkekirill(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: why there is not VACUUM FULL CONCURRENTLY?
Date: 2025-06-30 18:22:05
Message-ID: 152010.1751307725@localhost
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Antonin Houska <ah(at)cybertec(dot)at> wrote:

> jian he <jian(dot)universality(at)gmail(dot)com> wrote:
>
> > On Fri, Apr 11, 2025 at 5:28 PM Antonin Houska <ah(at)cybertec(dot)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.

v15 is attached. Just rebased so it applies to the current HEAD.

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

Attachment Content-Type Size
v15-0001-Add-REPACK-command.patch text/x-diff 82.7 KB
v15-0002-Move-conversion-of-a-historic-to-MVCC-snapshot-to-a-.patch text/x-diff 5.4 KB
v15-0003-Move-the-recheck-branch-to-a-separate-function.patch text/x-diff 4.8 KB
v15-0004-Add-CONCURRENTLY-option-to-REPACK-command.patch text/plain 150.0 KB
v15-0005-Add-regression-tests.patch text/x-diff 10.4 KB
v15-0006-Introduce-repack_max_xlock_time-configuration-variab.patch text/x-diff 20.1 KB
v15-0007-Enable-logical-decoding-transiently-only-for-REPACK-.patch text/x-diff 35.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Álvaro Herrera 2025-06-30 18:27:28 Re: ALTER TABLE ALTER CONSTRAINT misleading error message
Previous Message Jacob Champion 2025-06-30 17:58:53 Re: BackendKeyData is mandatory?