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

From Antonin Houska
Subject Re: why there is not VACUUM FULL CONCURRENTLY?
Date
Msg-id 117560.1749464355@localhost
Whole thread Raw
In response to Re: why there is not VACUUM FULL CONCURRENTLY?  (jian he <jian.universality@gmail.com>)
List pgsql-hackers
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


Attachment

pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: Enhance pg_createsubscriber to create required standby.
Next
From: Xiaoran Wang
Date:
Subject: Re: [PATCH] Refactor: Extract XLogRecord info