From: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | andreas(at)proxel(dot)se, tomas(dot)vondra(at)2ndquadrant(dot)com, eldmannen(at)gmail(dot)com, mark(dot)kirkwood(at)catalyst(dot)net(dot)nz, michael(at)paquier(dot)xyz, chris(dot)travers(at)adjust(dot)com, ishii(at)sraoss(dot)co(dot)jp, alvherre(at)2ndquadrant(dot)com, euler(at)timbira(dot)com(dot)br, rjuju123(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: PostgreSQL pollutes the file system |
Date: | 2019-03-29 01:04:07 |
Message-ID: | 20190329.100407.1159785913847835944.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-pkg-debian |
> Andreas Karlsson <andreas(at)proxel(dot)se> writes:
>> On 3/27/19 3:26 PM, Tomas Vondra wrote:
>>> That is true, of course. But are there actual examples of such conflicts
>>> in practice? I mean, are there tools/packages that provide commands with
>>> a conflicting name? I'm not aware of any, and as was pointed before, we'd
>>> have ~20 years of history on any new ones.
>
>> That is a fair argument. Since we squatted those names back in the
>> mid-90s I think the risk of collision is low.
>
> Right. I think there is a fair argument to be made for user confusion
> (not actual conflict) with respect to createuser and dropuser. The
> argument for renaming any of the other tools is much weaker, IMO.
If we were to invent new command names, what about doing similar to
git? I mean something like:
pgsql createdb ....
Here, "pgsql" is new command name and "createdb" is a sub command name
to create a database.
This way, we would be free from the command name conflict problem and
plus, we could do:
pgsql --help
which will prints subscommand names when a user is not sure what is
the sub command name.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2019-03-29 01:05:52 | Re: pgsql: Compute XID horizon for page level index vacuum on primary. |
Previous Message | Tomas Vondra | 2019-03-29 00:56:48 | Re: Re: FETCH FIRST clause WITH TIES option |
From | Date | Subject | |
---|---|---|---|
Next Message | Fred .Flintstone | 2019-03-29 14:29:07 | Re: PostgreSQL pollutes the file system |
Previous Message | Fred .Flintstone | 2019-03-28 14:05:53 | Re: PostgreSQL pollutes the file system |