Re: Need to fix one more glitch in upgrade to -10.2

On 02/17/2018 04:44 PM, Rich Shepard wrote:
> On Sat, 17 Feb 2018, Adrian Klaver wrote:
> 
>> From a previous post:
>>
>> POSTGRES=/usr/lib${LIBDIRSUFFIX}/@PRGNAM@/$PG_VERSION/bin/postgres
>>
>> From here:
>>
>> http://slackbuilds.org/slackbuilds/14.1/system/postgresql/postgresql.SlackBuild 
>>
> 
>    The desktop runs 32-bit 14.2.
> 
>> You could also try using pg_ctl to start the server directly:
> 
>    postgres@salmo:~$ pg_ctl start -D /var/lib/pgsql/10.2/data/ waiting 
> for server to start....2018-02-17 16:43:18.344 PST [6761] LOG:  
> listening on IPv4 address "127.0.0.1", port 5432
> 2018-02-17 16:43:18.368 PST [6761] LOG:  listening on Unix socket 
> "/tmp/.s.PGSQL.5432"
> 2018-02-17 16:43:18.454 PST [6762] LOG:  database system was shut down 
> at 2018-02-17 15:53:32 PST
> 2018-02-17 16:43:18.487 PST [6761] LOG:  database system is ready to 
> accept connections
>   done
> server started
> postgres@salmo:~$ 2018-02-17 16:43:29.899 PST [6774] FATAL:  role 
> "rshepard" does not exist
> 2018-02-17 16:43:31.669 PST [6776] FATAL:  role "rshepard" does not exist
> 
>    So I guess I need to re-learn how to set roles and set one for me for 
> all
> databases I own. That's tomorrow morning. Will report results after doing
> that.

Got to thinking that given the issues with the upgrade I would be leery 
about the state of the new cluster as a whole. Might want to consider 
doing it over again or just use the pg_dumpall output to recreate the 
database(s).


> 
> Thanks, Adrian,
> 
> Rich
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com