.pgpass

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

.pgpass

PG Bug reporting form
The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/10/libpq-pgpass.html
Description:

I kindly suggest to let me edit this part to create examples such as
pg_restore -h HOST -p PORT -U SUPERUSERNAME -C -d postgres
DBtoRESTORE.BACKUPEXTENSION

this will be like generalized examples that users can replicate.

Thank you
Reply | Threaded
Open this post in threaded view
|

Re: .pgpass

Daniel Gustafsson
> On 10 Jan 2019, at 04:45, PG Doc comments form <[hidden email]> wrote:
>
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/10/libpq-pgpass.html
> Description:
>
> I kindly suggest to let me edit this part to create examples such as
> pg_restore -h HOST -p PORT -U SUPERUSERNAME -C -d postgres
> DBtoRESTORE.BACKUPEXTENSION
>
> this will be like generalized examples that users can replicate.

The documentation isn’t edited online, but is contained in the postgres source
repository.  If you want to edit it you will have to clone the repository and
propose a patch with your changes on the pgsql-docs mailinglist.  The “Working
with Git” article on the postgres wiki can be a good place to start if you are
new to working in the source repository.

cheers ./daniel
Reply | Threaded
Open this post in threaded view
|

Re: .pgpass

Michael Paquier-2
On Thu, Jan 10, 2019 at 11:02:08AM +0100, Daniel Gustafsson wrote:

> On 10 Jan 2019, at 04:45, PG Doc comments form <[hidden email]> wrote:
>> I kindly suggest to let me edit this part to create examples such as
>> pg_restore -h HOST -p PORT -U SUPERUSERNAME -C -d postgres
>> DBtoRESTORE.BACKUPEXTENSION
>>
>> this will be like generalized examples that users can replicate.
>
> The documentation isn’t edited online, but is contained in the postgres source
> repository.  If you want to edit it you will have to clone the repository and
> propose a patch with your changes on the pgsql-docs mailinglist.  The “Working
> with Git” article on the postgres wiki can be a good place to start if you are
> new to working in the source repository.
Before shaping a patch it is always possible to discuss the changes
you would like to do with the paragraphs you would like to introduce
as there is always room for improvements.  No, it is hard to
understand how you would like to improve things, why it makes sense,
and why the current set of examples is not enough to explain what you
are looking for.  The documentation needs to remain concise and a
maximum representative as well, so as any human reading it does not
get lost in a flow of useless information.  Based on the information
given in your initial mail, it is not really possible to see how at
least one of those points can be actually improved, so you need first
to bring more precisions on the matter.
--
Michael

signature.asc (849 bytes) Download Attachment