On Apr 4, 2013, at 2:11 PM, Tom Lane wrote:
> I think this should be addressed in extend.sgml not only on the CREATE
> EXTENSION reference page. After thinking awhile I came up with the
> attached wording. Further wordsmithing anyone?
Works for me, though I think it would be useful to have a t
Tom Lane writes:
> I think this should be addressed in extend.sgml not only on the CREATE
> EXTENSION reference page. After thinking awhile I came up with the
> attached wording. Further wordsmithing anyone?
Thanks!
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formatio
"David E. Wheeler" writes:
> On Apr 3, 2013, at 11:41 AM, Alvaro Herrera wrote:
>> Right -- an extension is not considered to live within a schema, they
>> are database-global. The objects might live in a particular schema (if
>> it is "relocatable"), and there's support to move those to a diffe
On Apr 4, 2013, at 5:16 AM, Dimitri Fontaine wrote:
> "David E. Wheeler" writes:
>> +Note that only the extension objects will be placed into the named
>> +schema; the extension itself is a database-global object.
>
> I think you're patching the right place, but I'm not sure abo
Hi,
I though we were more specific about an extension's object itself not
living in a schema in our documentation, but I agree we still have room
for progress here.
"David E. Wheeler" writes:
> +Note that only the extension objects will be placed into the named
> +schema; the ext
On Apr 3, 2013, at 11:41 AM, Alvaro Herrera wrote:
>> Oh, they are not unique per-schema? I guess they are global to the database
>> but then their objects are in the specified schema, then.
>
> Right -- an extension is not considered to live within a schema, they
> are database-global. The ob
David E. Wheeler wrote:
> On Apr 3, 2013, at 2:37 AM, Albe Laurenz wrote:
>
> > I'd expect one of the CREATE EXTENSION commands to succeed
> > and the others to block until the transaction is committed,
> > then to fail with 'extension "oracle_fdw" already exists'.
> >
> > If that is what happen
On Apr 3, 2013, at 2:37 AM, Albe Laurenz wrote:
> I'd expect one of the CREATE EXTENSION commands to succeed
> and the others to block until the transaction is committed,
> then to fail with 'extension "oracle_fdw" already exists'.
>
> If that is what happens, it's what I'd expect since
> extens
David E. Wheeler wrote:
> I am working on scripts to copy data from Oracle via oracle_fdw. They each do
> something like this:
>
> CREATE SCHEMA migrate_stuff;
> SET search_path TO migrate_stuff,public;
> CREATE EXTENSION oracle_fdw SCHEMA migrate_rules;
>
[...]
>
> Then I run them
Hackers,
I am working on scripts to copy data from Oracle via oracle_fdw. They each do
something like this:
CREATE SCHEMA migrate_stuff;
SET search_path TO migrate_stuff,public;
CREATE EXTENSION oracle_fdw SCHEMA migrate_rules;
CREATE SERVER oracle_stuff FOREIGN DATA WRAPPER ora
10 matches
Mail list logo
