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

From Andrew Dunstan
Subject Re: why there is not VACUUM FULL CONCURRENTLY?
Date
Msg-id ba22936b-60c2-460d-afef-378370e03e22@dunslane.net
Whole thread Raw
In response to Re: why there is not VACUUM FULL CONCURRENTLY?  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: why there is not VACUUM FULL CONCURRENTLY?
Re: why there is not VACUUM FULL CONCURRENTLY?
List pgsql-hackers
On 2025-01-09 Th 8:35 AM, Alvaro Herrera wrote:
>
> I'm not happy with the idea of having this new command be VACUUM (FULL
> CONCURRENTLY).  It's a bit of an absurd name if you ask me.  Heck, even
> VACUUM (FULL) seems a bit absurd nowadays.
>
> 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
>

My $0.02:

COMPACT tablename ...


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Include patch id in commitfest page
Next
From: Guillaume Lelarge
Date:
Subject: Re: explain analyze rows=%.0f