| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | "Fred (dot)Flintstone" <eldmannen(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, Joe Conway <mail(at)joeconway(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Christoph Berg <myon(at)debian(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Andreas Karlsson <andreas(at)proxel(dot)se>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>, Michael Paquier <michael(at)paquier(dot)xyz>, Chris Travers <chris(dot)travers(at)adjust(dot)com>, Euler Taveira <euler(at)timbira(dot)com(dot)br>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PostgreSQL pollutes the file system |
| Date: | 2019-04-12 13:36:59 |
| Message-ID: | OtzMBT5a3S6kyiekF-H3n0U69fcqWxwSgt4X4kMQ4fC142cLoOCso5UgyXDmjpJCC1g88VtANZFK-3rMxljxqNAUwsFW-9xTmS8rBR5K23Q=@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-pkg-debian |
On Friday, April 12, 2019 3:20 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> On 2019-Apr-12, Daniel Gustafsson wrote:
>
> > There are many good reasons for the changes proposed in this thread, but I'm
> > not sure if discoverability is one. Relying on autocompleting a filename to
> > figure out existing tooling for database maintenance and DBA type operations
> > seems like a fragile usecase.
> > If commandline discoverability is of importance, providing a summary of the
> > tools in "man postgresql" seems like a better option.
>
> The first comment in the LWN article:
> "It's broken and obviously a bad idea but we've been doing it for so long we
> shouldn't attempt to fix it"
>
> IMO the future is longer than the past, and has more users, so let's do
> it right instead of perpetuating the mistakes.
>
> ... unless you think PostgreSQL is going to become irrelevant before
> 2050.
Not at all, and as I said there are many good reasons for doing this. I just
don't think "discoverability" is the driver, since I consider that a different
thing from ease of use and avoid confusion with system tools etc (my reading of
that word is "finding something new", not "how did I spell that tool again").
cheers ./daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-04-12 13:43:34 | Re: Adding Unix domain socket path and port to pg_stat_get_wal_senders() |
| Previous Message | Alvaro Herrera | 2019-04-12 13:20:14 | Re: PostgreSQL pollutes the file system |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fred .Flintstone | 2019-04-12 14:56:58 | Re: PostgreSQL pollutes the file system |
| Previous Message | Alvaro Herrera | 2019-04-12 13:20:14 | Re: PostgreSQL pollutes the file system |