From: Antonin Houska <ah@cybertec.at>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
cc: 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>
Subject: Re: why there is not VACUUM FULL CONCURRENTLY?
In-reply-to: <202503251432.o6obtgywjow5@alvherre.pgsql>
References: <202503251432.o6obtgywjow5@alvherre.pgsql>
Comments: In-reply-to Alvaro Herrera <alvherre@alvh.no-ip.org>
   message dated "Tue, 25 Mar 2025 15:32:46 +0100."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6058.1743060030.1@localhost>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 27 Mar 2025 08:20:30 +0100
Message-ID: <6059.1743060030@localhost>
Archived-At: 
 <https://www.postgresql.org/message-id/6059.1743060030%40localhost>
Precedence: bulk

Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:

> On 2025-Mar-22, Antonin Houska wrote:
> =

> > Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> > =

> > > I rebased this patch series; here's v09.  No substantive changes fro=
m v08.
> > > I made sure the tree still compiles after each commit.
> =

> I rebased again, fixing a compiler warning reported by CI and applying
> pgindent to each individual patch.  I'm slowly starting to become more
> familiar with the whole of this new code.

I'm trying to reflect Robert's suggestions about locking [1]. The next ver=
sion
should be a bit simpler, so maybe wait for it before you continue studying=
 the
code.

[1] https://www.postgresql.org/message-id/CA%2BTgmobUZ0g%3D%3DSZv-OSFCQTGF=
Pis5Qz1UsiMn18HGOWzsiyOLQ%40mail.gmail.com

-- =

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