From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Fred .Flintstone <eldmannen@gmail.com>
Cc: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Andreas Karlsson <andreas@proxel.se>
Cc: Chris Travers <chris.travers@adjust.com>
Cc: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Euler Taveira <euler@timbira.com.br>
Cc: Julien Rouhaud <rjuju123@gmail.com>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: PostgreSQL pollutes the file system
Date: Wed, 27 Mar 2019 14:51:16 +0100
Message-ID: <20190327135116.GA17983@development> (raw)
In-Reply-To: <CAJgfmqXYYKXR+QUhEa3cq6pc8dV0Hu7QvOUccm7R0TkC=T-+=A@mail.gmail.com>
References: <754d8607-682e-6f59-6870-faee5fa0820c@2ndquadrant.com>
<20190321.084132.2186284141219540889.t-ishii@sraoss.co.jp>
<20190321004919.GE20192@paquier.xyz>
<CAN-RpxBfajcAmdP_ghBjXgGYq1f+vf_Em+P6LBqfCq=av2cumg@mail.gmail.com>
<fdbcadf7-9edd-b20d-9987-4e7d21d23b2d@proxel.se>
<10036.1553176960@sss.pgh.pa.us>
<20190322003611.GK20192@paquier.xyz>
<31754.1553220346@sss.pgh.pa.us>
<3edd2644-eaf2-41e0-aa7a-92786d25b29c@catalyst.net.nz>
<CAJgfmqXYYKXR+QUhEa3cq6pc8dV0Hu7QvOUccm7R0TkC=T-+=A@mail.gmail.com>
On Wed, Mar 27, 2019 at 02:31:14PM +0100, Fred .Flintstone wrote:
>Many of these are gone in the modern PostgreSQL, a few remain.
>https://packages.ubuntu.com/disco/amd64/postgresql-client-11/filelist
>
>/usr/lib/postgresql/11/bin/clusterdb
>/usr/lib/postgresql/11/bin/createdb
>/usr/lib/postgresql/11/bin/createuser
>/usr/lib/postgresql/11/bin/dropdb
>/usr/lib/postgresql/11/bin/dropuser
>/usr/lib/postgresql/11/bin/pg_basebackup
>/usr/lib/postgresql/11/bin/pg_dump
>/usr/lib/postgresql/11/bin/pg_dumpall
>/usr/lib/postgresql/11/bin/pg_isready
>/usr/lib/postgresql/11/bin/pg_receivewal
>/usr/lib/postgresql/11/bin/pg_recvlogical
>/usr/lib/postgresql/11/bin/pg_restore
>/usr/lib/postgresql/11/bin/psql
>/usr/lib/postgresql/11/bin/reindexdb
>/usr/lib/postgresql/11/bin/vacuumdb
>
>Can we rename clusterdb, reindexdb and vacuumdb to carry the pg_ prefix?
>
I think the consensus in this thread (and the previous ancient ones) is
that it's not worth it. It's one thing to introduce new commands with the
pg_ prefix, and it's a completely different thing to rename existing ones.
That has inherent costs, and as Tom pointed out the burden would fall on
people using PostgreSQL (and that's rather undesirable).
I personally don't see why having commands without pg_ prefix would be
an issue. Especially when placed in a separate directory, which eliminates
the possibility of conflict with other commands.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-pkg-debian@postgresql.org
Cc: tomas.vondra@2ndquadrant.com, eldmannen@gmail.com, mark.kirkwood@catalyst.net.nz, tgl@sss.pgh.pa.us, michael@paquier.xyz, andreas@proxel.se, chris.travers@adjust.com, ishii@sraoss.co.jp, alvherre@2ndquadrant.com, euler@timbira.com.br, rjuju123@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: PostgreSQL pollutes the file system
In-Reply-To: <20190327135116.GA17983@development>
References: <754d8607-682e-6f59-6870-faee5fa0820c@2ndquadrant.com> <20190321.084132.2186284141219540889.t-ishii@sraoss.co.jp> <20190321004919.GE20192@paquier.xyz> <CAN-RpxBfajcAmdP_ghBjXgGYq1f+vf_Em+P6LBqfCq=av2cumg@mail.gmail.com> <fdbcadf7-9edd-b20d-9987-4e7d21d23b2d@proxel.se> <10036.1553176960@sss.pgh.pa.us> <20190322003611.GK20192@paquier.xyz> <31754.1553220346@sss.pgh.pa.us> <3edd2644-eaf2-41e0-aa7a-92786d25b29c@catalyst.net.nz> <CAJgfmqXYYKXR+QUhEa3cq6pc8dV0Hu7QvOUccm7R0TkC=T-+=A@mail.gmail.com> <20190327135116.GA17983@development>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox