Re: Upgrading using pg_dumpall [FIXED]

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Rich Shepard <rshepard(at)appl-ecosys(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Upgrading using pg_dumpall [FIXED]
Date: 2016-09-04 16:10:58
Message-ID: b632f0a3-093f-7302-1878-18b4bd03d9f0@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 09/04/2016 09:01 AM, Rich Shepard wrote:
> On Sun, 4 Sep 2016, Adrian Klaver wrote:
>
>> 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
>
> Adrian,
>
> I saw that but missed the meaning. I'm the only user on this system so
> there is no internal security risk.

Just be aware that you now have a password for the postgres user and
that if you ever do enable md5 you will need it. I would take Charles's
suggestion and set up a .pgpass file just to be safe.

>
> After learning that the Slackware script's restart does not work[1] I
> stopped the process then restarted it. I can now access my databases and
> the
> financial software via the browser UI.
>
> Now I can remove the 9.3.4 directory and be comfortable that the next
> upgrade will be smooth.
>
> Thanks very much for your patient help!
>
> Much appreciated,
>
> Rich
>
> [1] I've seen this same behavior in other rc.<program> scripts. Stopping
> and starting works in all cases.
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2016-09-04 16:18:32 Re: Upgrading using pg_dumpall [FIXED]
Previous Message Rich Shepard 2016-09-04 16:07:59 Re: Upgrading using pg_dumpall