Re: pg_execute_from_file review - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: pg_execute_from_file review
Date
Msg-id E5827EF1-E589-42FF-8237-5906031E9262@kineticode.com
Whole thread Raw
In response to Re: pg_execute_from_file review  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
On Dec 7, 2010, at 1:17 PM, Dimitri Fontaine wrote:

>> Anyway, in a less blue-sky vein: we could fix some of these problems by
>> having an explicit relocatable-or-not property for extensions.  If it is
>> relocatable, it's required to keep all its owned objects in the target
>> schema, and ALTER EXTENSION .. SET SCHEMA is allowed; else not.  This
>> does nothing for the fix-the-search_path-property problem, though.
> 
> The search_path is the complex (as in AI complete) part of it, but given
> your idea here, we could make it so that only the non-relocatable
> extensions benefit from the @extschema@ placeholder.

+1

That might be an appropriate compromise.

Best,

David



pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: Review: Extensions Patch
Next
From: Tom Lane
Date:
Subject: Re: pg_execute_from_file review