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

From Michael Paquier
Subject Re: why there is not VACUUM FULL CONCURRENTLY?
Date
Msg-id ZbmA6Vxgg1VmLcIh@paquier.xyz
Whole thread Raw
In response to Re: why there is not VACUUM FULL CONCURRENTLY?  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
On Tue, Jan 30, 2024 at 12:37:12PM +0100, Alvaro Herrera wrote:
> On 2024-Jan-30, Pavel Stehule wrote:
>
> > some basic variant (without autovacuum support) can be good enough. We have
> > no autovacuum support for REINDEX CONCURRENTLY and I don't see a necessity
> > for it (sure, it can be limited by my perspective) . The necessity of
> > reducing table size is not too common (a lot of use cases are better
> > covered by using partitioning), but sometimes it is, and then buildin
> > simple available solution can be helpful.
>
> That's my thinking as well.

Or, yes, I'd agree about that.  This can make for a much better user
experience.  I'm just not sure how that stuff would be shaped and how
much ground it would need to cover.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Incorrect cost for MergeAppend
Next
From: Tom Lane
Date:
Subject: Re: 003_extrafiles.pl test fails on Windows with the newer Perl versions