pg.ddx.io  pgsql-pkg-debian@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Howard <chris@elfpen.com>
To: pgsql-hackers@lists.postgresql.org
Subject: Re: PostgreSQL pollutes the file system
Date: Wed, 20 Mar 2019 09:17:29 -0500
Message-ID: <1813bb47-ff0c-6d19-7e27-abd5688719a8@elfpen.com> (raw)
In-Reply-To: <CAJgfmqV2N01PqLYMHswT2cQW28u-O8NZs5bVFYun6eQPc8psPg@mail.gmail.com>
References: <CAJgfmqUeyn2hhpuxCDCb3F7j=JhtU4SwGT3f0EhK5D1xpj1LAQ@mail.gmail.com>
	<7b9b6804-1575-3502-d9c9-91d324c913bd@proxel.se>
	<CAJgfmqV2N01PqLYMHswT2cQW28u-O8NZs5bVFYun6eQPc8psPg@mail.gmail.com>


Another pattern is to have a separate bin path for
various software packages:  /opt/postgres/bin  for example.

That doesn't directly answer "what is createdb?" but it
does give a quicker indication via the 'which' command.




On 3/20/19 5:43 AM, Fred .Flintstone wrote:
> It seems nothing came out of the discussion in 2008.
> I feel the topic should be revisited.
>
> I am in favor of doing so too. The deprecation cycle could involve
> symlinks for a brief period of time or a couple of versions.
>
> Yes, the wrapper script approach is used by Git as well as the "dotnet" command.
> The wrapper script addition doesn't mean executing the commands
> directly without the wrapper won't be possible. So one doesn't exclude
> the other.
> It would be a welcome addition.
>
> On Wed, Mar 20, 2019 at 11:05 AM Andreas Karlsson <andreas@proxel.se> wrote:
>> On 3/19/19 11:19 AM, Fred .Flintstone wrote:
>>> PostgreSQL pollutes the file system with lots of binaries that it is
>>> not obvious that they belong to PostgreSQL.
>>>
>>> Such as "/usr/bin/createdb", etc.
>>>
>>> It would be better if these files were renamed to be prefixed with
>>> pg_, such as pg_createdb.
>>> Or even better postgresql-createdb then be reachable by through a
>>> "postgresql" wrapper script.
>> Hi,
>>
>> This topic has been discussed before e.g. in 2008 in
>> https://www.postgresql.org/message-id/47EA5CC0.8040102%40sun.com and
>> also more recently but I cannot find it in the archives right now.
>>
>> I am personally in favor of renaming e.g. createdb to pg_createdb, since
>> it is not obvious that createdb belongs to PostgreSQL when reading a
>> script or looking in /usr/bin, but we would need a some kind of
>> deprecation cycle here or we would suddenly break tons of people's scripts.
>>
>> And as for the git-like solution with a wrapper script, that seems to be
>> the modern way to do things but would be an even larger breakage and I
>> am not convinced the advantage would be worth it especially since our
>> executables are not as closely related and consistent as for example git's.
>>
>> Andreas
>
>





view thread (113+ messages)  latest in thread

Message-ID: <1813bb47-ff0c-6d19-7e27-abd5688719a8@elfpen.com>
Permalink:  ../1813bb47-ff0c-6d19-7e27-abd5688719a8@elfpen.com/
Also on:    postgresql.org/message-id/1813bb47-ff0c-6d19-7e27-abd5688719a8@elfpen.com

 · 

reply

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: chris@elfpen.com, pgsql-hackers@lists.postgresql.org
  Subject: Re: PostgreSQL pollutes the file system
  In-Reply-To: <1813bb47-ff0c-6d19-7e27-abd5688719a8@elfpen.com>
  References: <CAJgfmqUeyn2hhpuxCDCb3F7j=JhtU4SwGT3f0EhK5D1xpj1LAQ@mail.gmail.com> <7b9b6804-1575-3502-d9c9-91d324c913bd@proxel.se> <CAJgfmqV2N01PqLYMHswT2cQW28u-O8NZs5bVFYun6eQPc8psPg@mail.gmail.com> <1813bb47-ff0c-6d19-7e27-abd5688719a8@elfpen.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