Re: PostgreSQL pollutes the file system

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andreas Karlsson <andreas(at)proxel(dot)se>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, "Fred (dot)Flintstone" <eldmannen(at)gmail(dot)com>, Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>, Michael Paquier <michael(at)paquier(dot)xyz>, Chris Travers <chris(dot)travers(at)adjust(dot)com>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Euler Taveira <euler(at)timbira(dot)com(dot)br>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PostgreSQL pollutes the file system
Date: 2019-03-27 14:41:27
Message-ID: 18182.1553697687@sss.pgh.pa.us
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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2019-03-27 14:45:18 Re: jsonpath
Previous Message Alexander Korotkov 2019-03-27 14:37:40 Re: jsonpath

Browse pgsql-pkg-debian by date

  From Date Subject
Next Message Alvaro Herrera 2019-03-27 14:52:29 Re: PostgreSQL pollutes the file system
Previous Message Andreas Karlsson 2019-03-27 14:36:07 Re: PostgreSQL pollutes the file system