Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 59EF76348EA for ; Mon, 13 Sep 2010 19:17:59 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 38947-05 for ; Mon, 13 Sep 2010 22:17:50 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from momjian.us (momjian.us [70.90.9.53]) by mail.postgresql.org (Postfix) with ESMTP id 0003462DBEC for ; Mon, 13 Sep 2010 19:17:21 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id o8DMHM624022; Mon, 13 Sep 2010 18:17:22 -0400 (EDT) From: Bruce Momjian Message-Id: <201009132217.o8DMHM624022@momjian.us> Subject: Re: pg_upgrade 9b4 -> 9rc1 odd behavior with -u (non-)postgres In-Reply-To: To: Lou Picciano Date: Mon, 13 Sep 2010 18:17:22 -0400 (EDT) CC: pgsql-testers@postgresql.org X-Mailer: ELM [version 2.4ME+ PL124 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201009/20 X-Sequence-Number: 196 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 http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +