From: Bruce Momjian <bruce@momjian.us>
To: Lou Picciano <LouPicciano@comcast.net>
Cc: pgsql-testers@postgresql.org
Subject: Re: pg_upgrade 9b4 -> 9rc1 odd behavior with -u (non-)postgres
Date: Mon, 13 Sep 2010 18:17:22 -0400 (EDT)
Message-ID: <201009132217.o8DMHM624022@momjian.us> (raw)
In-Reply-To: <C4F918FB-5C91-4CE4-AE98-B4D894A5EEE5@comcast.net>
Lou Picciano wrote:
> [TEST REPORT]
> [Release]: 9.0 RC1
> [Test Type]: pg_upgrade: 9.0-beta4 (Cluster 'A') -> 9.0-RC1 (Cluster 'B') user 'non'-postgres.
> [Test]: pg_upgrade (...options...) -u master
> [Platform]: Solaris 10 - Sun E450 Quad
> [Parameters]: Our administrator role is 'master' in both clusters. User 'master' has been created in Cluster B, SUPERUSER LOGIN CREATEROLE CREATEDB, and has been given 'trust' access. Logging turned on in config. Otherwise, cluster has been left in 'initdb' condition.
> [Failure]: YES.
> [Results]: Script connect to Database 'A' and dumps catalog, apparently without error.
> Connects to Database 'B', crashes on attempt to create user 'postgres' - which, of course, already exists. Any subsequent run crashes on attempt to create 'first' user in cluster, already created in prior run.
> [Comments]: Collation and encoding significant? # initdb -D /cloud/rc1 -E UTF8 --locale=en_US.UTF-8 (to be sure Cluster B encoding and 'lc_collate' matches that of Cluster A)
> DEBUG: autovacuum: processing database "postgres"
> WARNING: some databases have not been vacuumed in over 2 billion transactions
> DETAIL: You might have already suffered transaction-wraparound data loss.
>
> (really looking forward to being able to use pg_upgrade; looks like it will save a lot of work!)
Did you run initdb with --username?
initdb --username=master
I am thinking you didn't because it says the 'postgres' user already
exists in the new cluster. Also, please show me the exact error
message.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-testers@postgresql.org
Cc: bruce@momjian.us, LouPicciano@comcast.net
Subject: Re: pg_upgrade 9b4 -> 9rc1 odd behavior with -u (non-)postgres
In-Reply-To: <201009132217.o8DMHM624022@momjian.us>
References: <C4F918FB-5C91-4CE4-AE98-B4D894A5EEE5@comcast.net> <201009132217.o8DMHM624022@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox