Re: BUG #11090: Unclear error message in pg_upgrade

From: David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #11090: Unclear error message in pg_upgrade
Date: 2014-07-29 20:44:18
Message-ID: 1406666658960-5813221.post@n5.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

John R Pierce wrote
> On 7/29/2014 11:58 AM, Alvaro Herrera wrote:
>>

> brorfred@

> wrote:
>>
>>> >pg_upgrade requires that the old and new database has the same install
>>> >superuser (superuser that ran initdb). If this requirement isn't
>>> fulfilled,
>>> >you'll get the following error:
>>> >
>>> >"Old and new cluster install users have different values for
>>> >pg_authid.oid.\n"
>> To me, the bug is that we required both superusers to be named the same
>> in the first place.
>
> so, if its enhanced with a -U newsuperuser flag, any objects owned by
> 'postgres' on the original cluster are now owned by 'newsuperuser' on
> the new cluster?

Please no. I'm not a pg_upgrade user but this just seems like asking for
trouble. There has been one complaint and while I can see why the user
tried this it is not a very convincing use case. Rewording the error is
sufficient.

David J.

--
View this message in context: http://postgresql.1045698.n5.nabble.com/BUG-11090-Unclear-error-message-in-pg-upgrade-tp5813198p5813221.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jeff Janes 2014-07-29 20:57:31 Re: BUG #11090: Unclear error message in pg_upgrade
Previous Message David G Johnston 2014-07-29 20:40:45 Re: BUG #11090: Unclear error message in pg_upgrade