Re: Move cluster to new host, upgraded version [DONE] - Mailing list pgsql-general

From Rich Shepard
Subject Re: Move cluster to new host, upgraded version [DONE]
Date
Msg-id alpine.LNX.2.20.1811140801300.26515@salmo.appl-ecosys.com
Whole thread Raw
In response to Re: Move cluster to new host, upgraded version  (Rich Shepard <rshepard@appl-ecosys.com>)
List pgsql-general
On Wed, 14 Nov 2018, Rich Shepard wrote:

> I think that I FUBARed the upgrade from 10.3 to 11.1. I've removed both
> packages and am rebuilding 11.1. I'll install it, run initdb on it, then
> re-run pg_dumpall on the 10.5 data directory on the old desktop. Starting
> from scratch on this new desktop will save time for all of us.

   All fixed now. To complete the thread this is what I did:

   1) Removed Slackware packages for postgresql-10.3 and -11.1.
   2) Removed /var/lib/pgsql/10.3 and 11.1.
   3) Re-built postgresql-11.1 and re-installed it.
   4) As user 'postgres' ran initdb and pg_ctl start pointing to
     /var/lib/pgsql/11/data.
   5) Edited postgresql.conf and pg_hba.conf to accept connections from all
     hosts on the LAN.
   6) Re-started postgres.
   7) As 'postgre' ran
     pg_dumpall -h salmo -c -f pg-all-2018-11-14.sql
   8) Then postgres ran
     psql -f pg-all-2018-11-14.sql

   Now I, as a user, can access my databases without a password.

   Thank you, Adrian, for your patient help. And you, Tom, for your helpful
comment.

Best regards,

Rich


pgsql-general by date:

Previous
From: Ron
Date:
Subject: Re: Default Privilege Table ANY ROLE
Next
From: Jean-Marc Lessard
Date:
Subject: RE: pg_dump out of memory for large table with LOB