Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created
Date
Msg-id 20120710214326.GA6315@momjian.us
Whole thread Raw
In response to Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created  (Maciek Sakrejda <m.sakrejda@gmail.com>)
Responses Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created  (Daniel Farina <daniel@heroku.com>)
Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created  (cowwoc <cowwoc@bbs.darktech.org>)
List pgsql-bugs
On Tue, Jul 10, 2012 at 01:03:18PM -0700, Maciek Sakrejda wrote:
> So, is there hope of a better fix here for 9.2 (specifically for
> preserving extension ownership on pg_upgrade and dump/restore, though
> I understand it may not make sense to do that if we can't fix a number
> of related issues)? If not, is the below catalog-twiddling sane,
> lacking an ALTER EXTENSION foo OWNER TO ...?
>
> postgres=# update pg_extension set extowner = (select oid from
> pg_roles where rolname = 'maciek') where extname = 'plpgsql';

There is no hope that any changes to extensions will be preserved across
upgrades any better than it was in 9.1 --- the change is only that
pg_upgrade will not fail.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

pgsql-bugs by date:

Previous
From: Maciek Sakrejda
Date:
Subject: Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created
Next
From: Daniel Farina
Date:
Subject: Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created