Re: PostgreSQL pollutes the file system - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: PostgreSQL pollutes the file system
Date
Msg-id 2b6890db-acca-8f44-de4f-f43d70d57000@2ndquadrant.com
Whole thread Raw
In response to Re: PostgreSQL pollutes the file system  (Michael Paquier <michael@paquier.xyz>)
Responses Re: PostgreSQL pollutes the file system
List pgsql-hackers

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


pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: MSVC Build support with visual studio 2019
Next
From: Haribabu Kommi
Date:
Subject: Re: current_logfiles not following group access and instead followslog_file_mode permissions