From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, jeff <jeff(at)pgexperts(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #6704: ALTER EXTENSION postgis SET SCHEMA leaves dangling relations |
Date: | 2012-08-31 04:47:54 |
Message-ID: | 1346388417-sup-7175@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Excerpts from Tom Lane's message of jue ago 30 23:19:12 -0400 2012:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > On Fri, Jun 22, 2012 at 10:37:10PM -0400, Tom Lane wrote:
> >> jeff(at)pgexperts(dot)com writes:
> >>> DROP and CREATE extension appear to work fine, but if you ALTER EXTENSION
> >>> postgis SET SCHEMA foo, it leaves a few relations behind.
>
> >> What it seems to be leaving behind is indexes ... also relation rowtypes.
>
> > Uh, did this get fixed? I can't find a commit related to the fix.
>
> No, it's still an open issue.
Hmm, I think this might be my bug. I will have a look at this; not sure
if I'll be able to do it tomorrow, though (and certainly not during the
weekend).
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Rikard Pavelic | 2012-08-31 07:32:13 | Re: BUG #6489: Alter table with composite type/table |
Previous Message | Tom Lane | 2012-08-31 03:19:12 | Re: BUG #6704: ALTER EXTENSION postgis SET SCHEMA leaves dangling relations |