pg.ddx.io  pgsql-pkg-debian@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Michael Paquier <michael@paquier.xyz>
To: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: alvherre@2ndquadrant.com
Cc: euler@timbira.com.br
Cc: tgl@sss.pgh.pa.us
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: Thu, 21 Mar 2019 02:32:23 +0100
Message-ID: <2b6890db-acca-8f44-de4f-f43d70d57000@2ndquadrant.com> (raw)
In-Reply-To: <20190321004919.GE20192@paquier.xyz>
References: <20190320180832.GA11614@alvherre.pgsql>
	<754d8607-682e-6f59-6870-faee5fa0820c@2ndquadrant.com>
	<20190321.084132.2186284141219540889.t-ishii@sraoss.co.jp>
	<20190321004919.GE20192@paquier.xyz>



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? On
>>> my system, there are ~1400 binaries in /usr/bin, and for the vast
>>> majority of them it's rather unclear where do they come from.
> 
> Naming conflict because our binary names are too generic?  createdb
> could for example be applied to any database, and not only Postgres.
> (I have 1600 entries in /usr/bin on a Debian installation.)
> 

Maybe. Do we actually know about such cases? Also, isn't setting
--prefix a suitable solution? I mean, it's what we/packagers do to
support installing multiple Pg versions (in which case it'll conflict no
matter how we rename stuff) anyway.


regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




view thread (113+ messages)  latest in thread

Message-ID: <2b6890db-acca-8f44-de4f-f43d70d57000@2ndquadrant.com>
Permalink:  ../2b6890db-acca-8f44-de4f-f43d70d57000@2ndquadrant.com/
Also on:    postgresql.org/message-id/2b6890db-acca-8f44-de4f-f43d70d57000@2ndquadrant.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: tomas.vondra@2ndquadrant.com, michael@paquier.xyz, ishii@sraoss.co.jp, alvherre@2ndquadrant.com, euler@timbira.com.br, tgl@sss.pgh.pa.us, 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: <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>

* 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