From: Michael Paquier <michael@paquier.xyz>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: aleon1220@gmail.com
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: .pgpass
Date: Thu, 10 Jan 2019 20:24:32 +0900
Message-ID: <20190110112432.GO2157@paquier.xyz> (raw)
In-Reply-To: <781EBDA7-16F8-496C-B96E-D7CDADE6E51E@yesql.se>
References: <154709193735.22759.14024284152766029001@wrigleys.postgresql.org>
<781EBDA7-16F8-496C-B96E-D7CDADE6E51E@yesql.se>
On Thu, Jan 10, 2019 at 11:02:08AM +0100, Daniel Gustafsson wrote:
> On 10 Jan 2019, at 04:45, PG Doc comments form <noreply@postgresql.org> 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
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: michael@paquier.xyz, daniel@yesql.se, aleon1220@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: .pgpass
In-Reply-To: <20190110112432.GO2157@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox