From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #11090: Unclear error message in pg_upgrade |
Date: | 2014-07-29 20:57:31 |
Message-ID: | CAMkU=1zDN8mCfXRvLtTyTYuwM6VdCPhVZGMVR3ooxGm-hf9Omw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Jul 29, 2014 at 1:44 PM, David G Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> 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.
>
I have one database with a retrospectively poor choice of initdb -U. I
certainly wish there was a way, short of dump and restore, to change the
name of that user. Although I don't think pg_upgrade would be the ideal
way to do that.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2014-07-29 21:04:40 | Re: BUG #11090: Unclear error message in pg_upgrade |
Previous Message | David G Johnston | 2014-07-29 20:44:18 | Re: BUG #11090: Unclear error message in pg_upgrade |