From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
---|---|
To: | Robert Treat <rob(at)xzilla(dot)net> |
Cc: | Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Antonin Houska <ah(at)cybertec(dot)at>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com> |
Subject: | Re: Adding REPACK [concurrently] |
Date: | 2025-08-22 09:40:40 |
Message-ID: | 202508220940.u6qkixbhu7xs@alvherre.pgsql |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2025-Aug-21, Robert Treat wrote:
> What's the plan for clusterdb? It seems like we'd ideally create a
> stand alone pg_repackdb which replaces clusterdb and also allows us to
> remove the FULL options from vacuumdb.
I don't think we should remove clusterdb, to avoid breaking any scripts
that work today. As you say, I would create the standalone pg_repackdb
to do what we need it to do (namely: run the REPACK commands) and leave
vacuumdb and clusterdb alone. Removing the obsolete commands and
options can be done in a few years.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Álvaro Herrera | 2025-08-22 09:46:45 | Re: misleading error message in ProcessUtilitySlow T_CreateStatsStmt |
Previous Message | Kirill Reshke | 2025-08-22 09:19:02 | Re: Add OID descriptions to dumped parse/query/plan trees |