Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created

From: Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created
Date: 2012-07-10 20:03:18
Message-ID: CAOtHd0C-mZUBRV1Wb6CE4thdVyysOfODYAaRKOQQX1etBT1M3A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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';

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2012-07-10 21:43:26 Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created
Previous Message Tom Lane 2012-07-10 04:08:03 Re: BUG #6723: Exception for correct query