Re: Upgrading using pg_dumpall - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Upgrading using pg_dumpall
Date
Msg-id e97b786b-8184-df3e-0003-ce8e42afed62@aklaver.com
Whole thread Raw
In response to Re: Upgrading using pg_dumpall  (Rich Shepard <rshepard@appl-ecosys.com>)
Responses Re: Upgrading using pg_dumpall [FIXED]  (Rich Shepard <rshepard@appl-ecosys.com>)
List pgsql-general
On 09/04/2016 07:07 AM, Rich Shepard wrote:
> On Sun, 4 Sep 2016, Adrian Klaver wrote:
>
>> The above is not possible. If the postmaster was not running there
>> would be no rejection error.
>
> Adrian,
>
>   Yes. I conflated when the postmaster was running -- using the 9.3.4
> server
> -- and now when it's not running. Now I'm wondering if I mistakenly used
> the
> -W option to initdb which requires password use for access.
>
>> Don't do that, you will end up right back at this point again. Find
>> the pg_hba.conf files for your 9.5 cluster and your 9.3 cluster and
>> post them here.
>
>   OK. But when I used 'diff -y' I saw only a paragraph of comments as
> different. I'll try attaching them; they're ~100 lines each. If the
> attachments are stripped off my the mlm I'll list them within the message
> body.

Actually there is an important difference. In your 9.3 file you have set
METHOD set to trust and in the 9.5 file it is set to md5, which is
password. Set the METHOD to trust in your 9.5 file and restart the
database. Now for the non-socket access methods this is a security risk,
so you will want to change it back at some point once you get  the
users/passwords figured out
>
> Rich
>
>
>
>
>


--
Adrian Klaver
adrian.klaver@aklaver.com


pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Upgrading using pg_dumpall
Next
From: Rich Shepard
Date:
Subject: Re: Upgrading using pg_dumpall