Re: why there is not VACUUM FULL CONCURRENTLY?
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Pavel Stehule <pavel.stehule@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2024-01-30T23:06:17Z
Lists: 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
Commits
-
Add CONCURRENTLY option to REPACK
- 28d534e2ae0a 19 (unreleased) landed
-
Introduce the REPACK command
- ac58465e0618 19 (unreleased) landed
-
Adjust signature of cluster_rel() and its subroutines
- cc811f92bac5 18.0 landed
-
Simplify signature of RewriteTable
- ebd8fc7e47fd 18.0 cited