Re: Upgrading using pg_dumpall - Mailing list pgsql-general

From Rich Shepard
Subject Re: Upgrading using pg_dumpall
Date
Msg-id alpine.LNX.2.11.1609040653330.5431@localhost
Whole thread Raw
In response to Upgrading using pg_dumpall  (Rich Shepard <rshepard@appl-ecosys.com>)
Responses Re: Upgrading using pg_dumpall  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
On Sun, 4 Sep 2016, Charles Clavadetscher wrote:

> Are you able to connect to the new instance with any user at all, e.g.
> with psql? If so you can use the command \du to list all users.

Charles,

   No. The postmaster is not running; trying to start it requires a password
which is also rejected.

   Since I have the pg_dumpall data in a large .sql file I think the best
solution is for me to remove the 9.5.4 package completely, re-install from
the package tarball, run initdb, then start the postmaster and restore all
the databases in the cluster.

   I'm thinking that without paying attention when I initially ran initdb I
used a commandline found on a web site (rather than just reading the man
page) and used the -W option which requires a password for everything. So
starting over from scratch _should_ remove all issues and successfully end
this thread.

Thanks,

Rich



pgsql-general by date:

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