Re: [HACKERS] Changing extension schema fails silently

2011-07-05 Thread Thom Brown
On 5 July 2011 21:27, Thom Brown t...@linux.com wrote: Hi, I'm using the latest head and I created the file_fdw extension, then attempted to change its schema (ALTER EXTENSION file_fdw SET SCHEMA new_schema.  No error was returned, but it remained in the same schema (according to

Re: [HACKERS] Changing extension schema fails silently

2011-07-05 Thread Peter Geoghegan
From the docs: Note that unlike most catalogs with a namespace column, extnamespace is not meant to imply that the extension belongs to that schema. Extension names are never schema-qualified. Rather, extnamespace indicates the schema that contains most or all of the extension's objects. If

Re: [HACKERS] Changing extension schema fails silently

2011-07-05 Thread Thom Brown
On 5 July 2011 22:31, Peter Geoghegan pe...@2ndquadrant.com wrote: From the docs: Note that unlike most catalogs with a namespace column, extnamespace is not meant to imply that the extension belongs to that schema. Extension names are never schema-qualified. Rather, extnamespace indicates

Re: [HACKERS] Changing extension schema fails silently

2011-07-05 Thread Tom Lane
Thom Brown t...@linux.com writes: Correction, the objects which belong to the extension do switch schema, but the properties of the extension itself indicate the extension is in a different schema. So rather than not working at all, it seems that it's just forgotten to update the pg_extension

Re: [HACKERS] Changing extension schema fails silently

2011-07-05 Thread Thom Brown
On 5 July 2011 23:00, Tom Lane t...@sss.pgh.pa.us wrote: Thom Brown t...@linux.com writes: Correction, the objects which belong to the extension do switch schema, but the properties of the extension itself indicate the extension is in a different schema.  So rather than not working at all, it