Message-ID: <67851b65.170a0220.2f4d00.41de@mx.google.com>
Sender: Michael Banck <mbanck@gmail.com>
Date: Mon, 13 Jan 2025 14:55:48 +0100
From: Michael Banck <mbanck@gmx.net>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
	Antonin Houska <ah@cybertec.at>, 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?
References: <202501091335.pn54a2ettbsi@alvherre.pgsql>
 <ba22936b-60c2-460d-afef-378370e03e22@dunslane.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ba22936b-60c2-460d-afef-378370e03e22@dunslane.net>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: 
 <https://www.postgresql.org/message-id/67851b65.170a0220.2f4d00.41de%40mx.google.com>
Precedence: bulk

Hi,

On Sat, Jan 11, 2025 at 09:01:54AM -0500, Andrew Dunstan wrote:
> On 2025-01-09 Th 8:35 AM, Alvaro Herrera wrote:
> > Maybe we should have a new toplevel command.  Some ideas that have been
> > thrown around:
> > 
> > - RETABLE (it's like REINDEX, but for tables)
> > - ALTER TABLE <tab> SQUEEZE
> > - SQUEEZE <table>
> > - VACUUM (SQUEEZE)
> > - VACUUM (COMPACT)
> > - MAINTAIN <tab> COMPACT
> > - MAINTAIN <tab> SQUEEZE

I don't like any of them a lot :-/

> COMPACT tablename ...

That sounds like it would compress content rather than just rewrite it
normally to get rid of bloat.

I think REORG (or REPACK, but that has not history elsewhere) would fit
best, we don't need to emulate the myriad of DB2 options...


Michael