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: Move cluster to new host, upgraded version |
Date: | 2018-11-14 00:38:07 |
Message-ID: | 7612d388-2bea-66ed-0bad-7c2ade410899@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/13/18 4:24 PM, Rich Shepard wrote:
> On Tue, 13 Nov 2018, Adrian Klaver wrote:
>
>> You have two options:
>>
>> 1) The preferred one. Keep the password and create a .pgpass file to
>> hold the password:
>> https://www.postgresql.org/docs/10/libpq-pgpass.html
>
> Adrian,
>
> That's database-specific if I read the manual page correctly.
No:
" Each of the first four fields can be a literal value, or *, which
matches anything. "
>
>> My guess is you had one on the other machine.
>
> Nope. I've been running postgres since 1997 and never used a password
> since I'm the only one using the databases.
>
>> 2) Change your auth method in pg_hba.conf:
>> https://www.postgresql.org/docs/10/client-authentication.html
>
> /var/lib/pgsql/11/data/pg_hba.conf has trust as the local authentication
If the record starts with local then that is for socket connections.
If you are connecting to a host e.g -h localhost then you need to look
at the host records.
> method for all databases. Perhaps I need to restart the server after
> loading
> the databases. Will try that.
>
> Thanks,
>
> Rich
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Rich Shepard | 2018-11-14 00:41:35 | Re: Move cluster to new host, upgraded version |
Previous Message | Rich Shepard | 2018-11-14 00:24:40 | Re: Move cluster to new host, upgraded version |