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

From Fred .Flintstone
Subject Re: PostgreSQL pollutes the file system
Date
Msg-id CAJgfmqVS4O5ET3WyQWFZ-1gNR+3DzzhVqxf97g1WH5D_MUbFMA@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL pollutes the file system  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I would be fine with that.
We can make an exception for psql.

As long as we get rid of:
* clusterdb
* createdb
* createuser
* dropdb
* dropuser
* reindexdb
* vacuumdb

On Wed, Mar 20, 2019 at 7:11 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> "Fred .Flintstone" <eldmannen@gmail.com> writes:
> > Even just creating symlinks would be a welcome change.
> > So the real binary is pg_foo and foo is a symoblic link that points to pg_foo.
> > Then at least I can type pg_<tab> and use tab auto-completion to find
> > everything related to PostgreSQL.
>
> You'd miss psql.  I think the odds of renaming psql are not
> distinguishable from zero: whatever arguments you might want to make
> about, say, renaming initdb perhaps not affecting too many scripts
> are surely not going to fly for psql.  So that line of argument
> isn't too convincing.
>
>                         regards, tom lane


pgsql-hackers by date:

Previous
From: "Jonathan S. Katz"
Date:
Subject: Re: PostgreSQL pollutes the file system
Next
From: "Jonathan S. Katz"
Date:
Subject: Re: PostgreSQL pollutes the file system