Re: Upgrading using pg_dumpall

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-03 23:11:45
Message-ID: ae1c146a-0b59-cdf8-fe75-11fd621e49a8@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 09/03/2016 04:01 PM, Rich Shepard wrote:
> On Sat, 3 Sep 2016, Adrian Klaver wrote:
>
>> Once you verify that the new instance is running and you can connect
>> to it then:
>
> Shut down 9.3.4 using pg_ctl stop as user postgres. Started 9.5.4 as user
> postgres using 'pg_ctl start /var/lib/pgsql/9.5/data &'.
>
>> psql -U some_user -d postgres -p 5442 -f your_dumpall.sql
>
> In /tmp there's only
> .s.PGSQL.5432= .s.PGSQL.5432.lock
> and since only 9.5.4 is now running that port should be available.

Did you change the port number in the 9.5 postgresql.conf and restart
the server?

Or if you are fine running the 9.5 instance at port 5432, what happens
if you do?:

psql -d postgres -U some_user -p 5432

>
> The above command failed when run as both me (as user owning/granted all
> privileges on all databases) and as superuser postgres.

What was the error message?

>
> Rich
>
>

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rich Shepard 2016-09-03 23:16:00 Re: Upgrading using pg_dumpall
Previous Message Rich Shepard 2016-09-03 23:01:43 Re: Upgrading using pg_dumpall