Downloads
Home   >   mailing lists

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 152010.1751307725@localhost
Whole thread Raw
In response to Re: why there is not VACUUM FULL CONCURRENTLY?  (Antonin Houska <ah@cybertec.at>)
List pgsql-hackers
Tree view 
Antonin Houska <ah@cybertec.at> wrote:

> 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.

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

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

pgsql-hackers by date:

Previous
From: Dean Rasheed
Date:
Subject: Re: Allow ON CONFLICT DO UPDATE to return EXCLUDED values
Next
From: Álvaro Herrera
Date:
Subject: Re: ALTER TABLE ALTER CONSTRAINT misleading error message