Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
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

pgsql-bugs by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group