Re: Problem with pg_upgrade (8.4 -> 9.0) due to ALTER DATABASE SET ROLE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Treat <rob(at)xzilla(dot)net>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Florian Pflug <fgp(at)phlo(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Problem with pg_upgrade (8.4 -> 9.0) due to ALTER DATABASE SET ROLE
Date: 2011-02-28 05:21:06
Message-ID: 14763.1298870466@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Treat <rob(at)xzilla(dot)net> writes:
> Did anything ever come of this discussion?

I think it's a TODO --- nothing done about it as yet, AFAIR.

> On one of the databases I
> was upgrading, I ran into a similar problem with roles that are set as
> roles. The problem seems to stem from pg_dumpall dumping roles in
> alphabetical order:

> CREATE ROLE asha;
> ALTER ROLE asha SET role TO 'omniti';
> .. sometime later ...
> CREATE ROLE omniti;

That seems like a pretty bizarre thing to do. Why would you want such a
setting?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-02-28 06:20:32 Re: wCTE: about the name of the feature
Previous Message Robert Treat 2011-02-28 04:38:10 Re: Problem with pg_upgrade (8.4 -> 9.0) due to ALTER DATABASE SET ROLE