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.
> A bit of looking shows that ALTER EXTENSION SET SCHEMA calls
> AlterObjectNamespace_oid on the table. AlterObjectNamespace_oid
> calls AlterRelationNamespaceInternal, and nothing else. In comparison,
> ALTER TABLE SET SCHEMA (AlterTableNamespace) calls
> AlterRelationNamespaceInternal and about four other things. I'm not
> sure if this was broken before the last round of refactoring in this
> area, but for sure it's broken now.
Uh, did this get fixed? I can't find a commit related to the fix.
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
+ It's impossible for everything to be true. +
In response to
pgsql-bugs by date
|Next:||From: Bruce Momjian||Date: 2012-08-30 22:07:47|
|Subject: Re: BUG #6712: PostgreSQL 9.2 beta2: alter table drop
constraint does not work on inherited master table|
|Previous:||From: Jeff Lake||Date: 2012-08-30 21:42:58|
|Subject: Re: Segmentation Fault V 9.1.5|