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

From Bruce Momjian
Subject Re: Problem with pg_upgrade (8.4 -> 9.0) due to ALTER DATABASE SET ROLE
Date
Msg-id 201101070308.p0738Tb05348@momjian.us
Whole thread Raw
In response to Re: Problem with pg_upgrade (8.4 -> 9.0) due to ALTER DATABASE SET ROLE  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Problem with pg_upgrade (8.4 -> 9.0) due to ALTER DATABASE SET ROLE  (Robert Treat <rob@xzilla.net>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > We could modify pg_dump to emit RESET AUTHORIZATION in --binary-upgrade
> > mode.  I am unclear if that might cause some other problems though.
> 
> I finally figured out what was really bugging me about that proposal:
> it's a one-shot hack for fixing one problem that could arise from
> non-default ALTER DATABASE/ALTER ROLE settings.  Who's to say there
> are not other such issues, either now or in the future?
> 
> It occurs to me that a more principled way to deal with this class of
> problems would be to delay restoring ALTER DATABASE/ALTER ROLE
> settings until after everything else is done.  Not sure what the
> implementation consequences of that would be.  Ideally we'd make
> pg_dumpall output work that way in general, not just for pg_upgrade.

Yep, it feels like a one-off that no one else will ever hit, and there
are certainly other ALTER DATABASE SET commands that could also obstruct
a restore.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Problem with pg_upgrade (8.4 -> 9.0) due to ALTER DATABASE SET ROLE
Next
From: Itagaki Takahiro
Date:
Subject: Re: system views for walsender activity