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

From Fred .Flintstone
Subject Re: PostgreSQL pollutes the file system
Date
Msg-id CAJgfmqVQWFM7F-JogWEo6MWGA8Oa8BtB4dYAo=y7X5q=SBd35A@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL pollutes the file system  ("Fred .Flintstone" <eldmannen@gmail.com>)
Responses Re: PostgreSQL pollutes the file system
List pgsql-hackers
It seems we do have a clear path forward on how to accomplish this and
implement this change.

1. Rename executables to carry the pg_ prefix.
2. Create symlinks from the old names to the new names.
3. Modify the executables to read argv[0] and print a warning if the
executable is called from the old name (symlink).

This seems technically feasible and easy.

How can we proceed?

On Tue, Apr 2, 2019 at 11:24 PM Fred .Flintstone <eldmannen@gmail.com> wrote:
>
> It looks like this thread is featured on LWN under the article:
> Program names and "pollution".
> https://lwn.net/
> https://lwn.net/Articles/784508/ (Subscription required)
>
> On Sat, Mar 30, 2019 at 12:27 PM Peter Eisentraut
> <peter.eisentraut@2ndquadrant.com> wrote:
> >
> > On 2019-03-29 20:32, Joe Conway wrote:
> > >   pg_util <command> <options>
> >
> > How is that better than just renaming to pg_$oldname?
> >
> > --
> > Peter Eisentraut              http://www.2ndQuadrant.com/
> > PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Andrey Borodin
Date:
Subject: Re: GSOC 2019 proposal 'WAL-G safety features'
Next
From: Christoph Berg
Date:
Subject: Re: PostgreSQL pollutes the file system