From: | "Fred (dot)Flintstone" <eldmannen(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Chris Travers <chris(dot)travers(at)adjust(dot)com>, Andreas Karlsson <andreas(at)proxel(dot)se>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PostgreSQL pollutes the file system |
Date: | 2019-03-20 19:14:04 |
Message-ID: | CAJgfmqVS4O5ET3WyQWFZ-1gNR+3DzzhVqxf97g1WH5D_MUbFMA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-pkg-debian |
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(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "Fred .Flintstone" <eldmannen(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Jonathan S. Katz | 2019-03-20 19:15:02 | Re: PostgreSQL pollutes the file system |
Previous Message | Jonathan S. Katz | 2019-03-20 19:13:00 | Re: PostgreSQL pollutes the file system |
From | Date | Subject | |
---|---|---|---|
Next Message | Jonathan S. Katz | 2019-03-20 19:15:02 | Re: PostgreSQL pollutes the file system |
Previous Message | Jonathan S. Katz | 2019-03-20 19:13:00 | Re: PostgreSQL pollutes the file system |