From: Reid Thompson <Reid.Thompson@omnicell.com>
To: pgsql-hackers@lists.postgresql.org <pgsql-hackers@lists.postgresql.org>
Subject: Re: PostgreSQL pollutes the file system
Date: Wed, 27 Mar 2019 15:02:29 +0000
Message-ID: <d8ab6f8b98713c241a8a9d862c88933058ef2364.camel@omnicell.com> (raw)
In-Reply-To: <044a865f-c0c2-70e4-f4d0-ec841d701fda@proxel.se>
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>
<044a865f-c0c2-70e4-f4d0-ec841d701fda@proxel.se>
On Wed, 2019-03-27 at 15:07 +0100, Andreas Karlsson wrote:
> [EXTERNAL SOURCE]
>
>
>
> On 3/27/19 2:51 PM, Tomas Vondra wrote:
> > 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.
>
> I buy that it may not be worth breaking tens of thousands of scripts to
> fix this, but I disagree about it not being an issue. Most Linux
> distributions add PostgreSQL's executables in to a directory which is in
> the default $PATH (/usr/bin in the case of Debian). And even if it would
> be installed into a separate directory there would still be a conflict
> as soon as that directory is added to $PATH.
>
> And I think that it is also relatively easy to confuse adduser and
> createuser when reading a script. Nothing about the name createuser
> indicates that it will create a role in an SQL database.
>
> Andreas
>
theres nothing about createuser or adduser( useradd on my system,
adduser doesn't exist on mine ) that indicates that either would/should
create a user in the system either. That's what man and -h/--help are
for. If you don't know what an executable does, don't invoke it until
you do. That's a basic premise for any executable.
reid
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: Reid.Thompson@omnicell.com, pgsql-hackers@lists.postgresql.org
Subject: Re: PostgreSQL pollutes the file system
In-Reply-To: <d8ab6f8b98713c241a8a9d862c88933058ef2364.camel@omnicell.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> <20190327135116.GA17983@development> <044a865f-c0c2-70e4-f4d0-ec841d701fda@proxel.se> <d8ab6f8b98713c241a8a9d862c88933058ef2364.camel@omnicell.com>
* 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