MIME-Version: 1.0
References: <202507262156.sb455angijk6@alvherre.pgsql>
 <202508191853.wofznwocbi5x@alvherre.pgsql>
In-Reply-To: <202508191853.wofznwocbi5x@alvherre.pgsql>
From: Robert Treat <rob@xzilla.net>
Date: Thu, 21 Aug 2025 18:06:13 -0400
Message-ID: 
 <CAJSLCQ1YvjRvjji29dNMiYy+JnseMZkDpx4Ui0zcpLdk8wviyg@mail.gmail.com>
Subject: Re: Adding REPACK [concurrently]
To: =?UTF-8?Q?=C3=81lvaro_Herrera?= <alvherre@kurilemu.de>
Cc: Pg Hackers <pgsql-hackers@lists.postgresql.org>,
 Antonin Houska <ah@cybertec.at>,
	Fujii Masao <masao.fujii@gmail.com>,
 Mihail Nikalayeu <mihailnikalayeu@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAJSLCQ1YvjRvjji29dNMiYy%2BJnseMZkDpx4Ui0zcpLdk8wviyg%40mail.gmail.com>
Precedence: bulk

On Tue, Aug 19, 2025 at 2:53=E2=80=AFPM =C3=81lvaro Herrera <alvherre@kuril=
emu.de> wrote:
> Note choice of shell command name: though all the other programs in
> src/bin/scripts do not use the "pg_" prefix, this one does; we thought
> it made no sense to follow the old programs as precedent because there
> seems to be a lament for the lack of pg_ prefix in those, and we only
> keep what they are because of their long history.  This one has no
> history.
>
> Still on pg_repackdb, the implementation here is to install a symlink
> called pg_repackdb which points to vacuumdb, and make the program behave
> differently when called in this way.  The amount of additional code for
> this is relatively small, so I think this is a worthy technique --
> assuming it works.  If it doesn't, Antonin proposed a separate binary
> that just calls some functions from vacuumdb.  Or maybe we could have a
> common source file that both utilities call.
>

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.


Robert Treat
https://xzilla.net