From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: alvherre@2ndquadrant.com
Cc: euler@timbira.com.br
Cc: rjuju123@gmail.com
Cc: chris.travers@adjust.com
Cc: andreas@proxel.se
Cc: eldmannen@gmail.com
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: PostgreSQL pollutes the file system
Date: Wed, 20 Mar 2019 23:22:53 -0400
Message-ID: <22151.1553138573@sss.pgh.pa.us> (raw)
In-Reply-To: <2b6890db-acca-8f44-de4f-f43d70d57000@2ndquadrant.com>
References: <20190320180832.GA11614@alvherre.pgsql>
<754d8607-682e-6f59-6870-faee5fa0820c@2ndquadrant.com>
<20190321.084132.2186284141219540889.t-ishii@sraoss.co.jp>
<20190321004919.GE20192@paquier.xyz>
<2b6890db-acca-8f44-de4f-f43d70d57000@2ndquadrant.com>
Tomas Vondra <tomas.vondra@2ndquadrant.com> writes:
> On 3/21/19 1:49 AM, Michael Paquier wrote:
>> On Thu, Mar 21, 2019 at 08:41:32AM +0900, Tatsuo Ishii wrote:
>>> Can someone describe a scenario where this (name of the binary not
>>> clearly indicating it's related postgres) causes issues in practice?
>> Naming conflict because our binary names are too generic?
> Maybe. Do we actually know about such cases?
More to the point, we have now got twenty+ years seniority on any other
package that might want those /usr/bin names. So a conflict is not
*really* going to happen, or at least it's not going to be our problem
if it does.
The whole thing is unfortunate, without a doubt, but it's still
unclear that renaming those programs will buy anything that's worth
the conversion costs. I'd be happy to pay said costs if it were all
falling to this project to do so ... but most of the pain will be
borne by other people.
regards, tom lane
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: tgl@sss.pgh.pa.us, tomas.vondra@2ndquadrant.com, michael@paquier.xyz, ishii@sraoss.co.jp, alvherre@2ndquadrant.com, euler@timbira.com.br, rjuju123@gmail.com, chris.travers@adjust.com, andreas@proxel.se, eldmannen@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: PostgreSQL pollutes the file system
In-Reply-To: <22151.1553138573@sss.pgh.pa.us>
References: <20190320180832.GA11614@alvherre.pgsql> <754d8607-682e-6f59-6870-faee5fa0820c@2ndquadrant.com> <20190321.084132.2186284141219540889.t-ishii@sraoss.co.jp> <20190321004919.GE20192@paquier.xyz> <2b6890db-acca-8f44-de4f-f43d70d57000@2ndquadrant.com> <22151.1553138573@sss.pgh.pa.us>
* 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