| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com> |
| 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 21:43:26 |
| Message-ID: | 20120710214326.GA6315@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Farina | 2012-07-10 23:04:57 | Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created |
| Previous Message | Maciek Sakrejda | 2012-07-10 20:03:18 | Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created |