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

From Michael Paquier
Subject Re: PostgreSQL pollutes the file system
Date
Msg-id 20190322003611.GK20192@paquier.xyz
Whole thread Raw
In response to Re: PostgreSQL pollutes the file system  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PostgreSQL pollutes the file system
List pgsql-hackers
On Thu, Mar 21, 2019 at 10:02:40AM -0400, Tom Lane wrote:
> So there seems like a real risk that taking away createuser would
> result in security holes, not just annoying-but-trivial script update
> work.  That puts me more in the camp of "if we're going to do anything,
> rename it with a pg_ prefix" than "if we're going to do anything,
> remove it".

Removing it would be a bad idea as it is very easy to mess up with
things in such cases.  As you mentioned, renaming the tools now would
create more pain than actually solving things, so that's a bad idea
anyway.

I would be curious to hear the reason why such tool names have been
chosen from the start.  The tools have been switched to C in 9e0ab71
from 2003, have been introduced by Peter Eisentraut as of 240e4c9 from
1999, and I cannot spot the thread from the time where this was
discussed.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Offline enabling/disabling of data checksums
Next
From: Michael Paquier
Date:
Subject: Re: pg_basebackup ignores the existing data directory permissions