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

From Fred .Flintstone
Subject Re: PostgreSQL pollutes the file system
Date
Msg-id CAJgfmqV8p-vBgZb4OrSJ9Txo1yshaLYC0U2k4hA8UxeXO90Xgw@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL pollutes the file system  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers
I would disagree.

Discoverability is important, and having a user space that is
intuitive and predictable.
With the discoverability exposed by pg_<tab> then you immediately find
out what is available.

One shouldn't have to delve down into manuals and books. Then forget
what that darn command was next time its needed, just to have to
return to the documentation again.

Preferably a wrapper around the tools could provide a summary for all
the tools, just like git --help.

On Fri, Apr 12, 2019 at 2:56 PM Daniel Gustafsson <daniel@yesql.se> wrote:
>
> On Friday, April 12, 2019 2:25 PM, Fred .Flintstone <eldmannen@gmail.com> wrote:
>
> > It would make the old commands more easily discoverable. Just type pg_
> > and press the tab key for auto-completion.
>
> 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.
>
> cheers ./daniel



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [PATCH v20] GSSAPI encryption support
Next
From: Masahiko Sawada
Date:
Subject: Re: Calling pgstat_report_wait_end() before ereport(ERROR)