From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
---|---|
To: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
Cc: | PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Extension Facility |
Date: | 2009-07-23 06:46:38 |
Message-ID: | 1A8488FF-11F2-4381-8577-ECC3B6A2EA94@kineticode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jul 22, 2009, at 11:46 AM, Dimitri Fontaine wrote:
> Here are from memory the problems we don't have a solution for yet:
> - how to give user the ability to install the extension's objects in
> another schema than the pg_extension default one
Was that not a part of your original proposal, or the ensuing
discussion? Hrm, perhaps not. So I suggest that we take your proposed
syntax:
create extension foo ...
And just allow it to take a schema-qualified argument like any other
SQL command:
create extension myschema.foo ...
> - how to provide extension author a way to have major PG version
> dependant code without having to implement and maintain a specific
> function in their install.sql file
For a lot of extensions this may not be necessary. So I don't think
I'd hold up an initial implementation waiting for this to be figured
out. My $0.02.
Best,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Nikhil Sontakke | 2009-07-23 06:55:39 | Re: [PATCH] DefaultACLs |
Previous Message | David E. Wheeler | 2009-07-23 06:44:13 | Re: extension facility (was: revised hstore patch) |