| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | aleon1220(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: .pgpass |
| Date: | 2019-01-10 10:02:08 |
| Message-ID: | 781EBDA7-16F8-496C-B96E-D7CDADE6E51E@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
> On 10 Jan 2019, at 04:45, PG Doc comments form <noreply(at)postgresql(dot)org> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-01-10 11:24:32 | Re: .pgpass |
| Previous Message | PG Doc comments form | 2019-01-10 03:45:37 | .pgpass |