From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Upgrading using pg_dumpall |
Date: | 2016-09-04 19:48:04 |
Message-ID: | 3d39e71a-5f3e-5f90-7169-92a8bb1ba067@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 09/04/2016 12:42 PM, Rich Shepard wrote:
> On Sun, 4 Sep 2016, Adrian Klaver wrote:
>
>> Well first, if you are going to use trust as your auth method then
>> specifying a password is moot exercise.
>
> I tried adding an explicit password to ~/.pgpass with md5 as the auth
> method, but that didn't work so I went back to trust. That's served well
> for
> 19 years. :-)
auth is not something you enter in .pgpass. The format for the file is
spelled out here:
https://www.postgresql.org/docs/9.5/static/libpq-pgpass.html
>
>> Second, not sure where you are in the process, but any time you change
>> the
>> pg_hba.conf file you will need to give Postgres a reload signal to get it
>> to recognize the changes. Again not sure how you are signalling Postgres
>> but if you are using pg_ctl
>> https://www.postgresql.org/docs/9.5/static/app-pg-ctl.html
>> then something like:
>>
>> pg_ctl reload -D path_to_your_datadir
>>
>> as OS user postgres.
>
> Good to know. I use pg_ctl stop and start with the path on both command
> lines.
>
>> Third, .pgpass should hold information that already exists in the
>> database
>> system tables. It is not a mechanism for entering that information into
>> the database. So yes, you will need to use ALTER ROLE to create the
>> password inside Postgres.
>
> OK. I'll try that for the learning experience.
>
> So much to learn and so little time ...
>
> Thanks,
>
> Rich
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Rich Shepard | 2016-09-04 19:55:35 | Re: Upgrading using pg_dumpall |
Previous Message | Adrian Klaver | 2016-09-04 19:43:55 | Re: Upgrading using pg_dumpall |