Re: Extensions User Design

From: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Extensions User Design
Date: 2009-06-25 07:58:25
Message-ID: 87bpocagny.fsf@hi-media-techno.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Re-reading in the morning rather that late at night...

Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> === installing and removing an extension
>>
>> begin;
>> install extension foo with search_path = foo;
>
> Needs install file location:
>
> INSTALL EXTENSION foo FROM '~/downloads/foo' WITH search_path = 'foo';

This would run the foo.sql file containing the CREATE EXTENSION call,
then run the install procedure itself which will run the author's
foo.install.sql script, right? I'm all for it.

Now, I'm not sure which form would pg_dump issue, maybe it should dumps
the CREATE EXTENSION and the INSTALL EXTENSION commands separately?

--
Dimitri Fontaine
PostgreSQL DBA, Architecte

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2009-06-25 08:24:40 Re: Extensions User Design
Previous Message Fujii Masao 2009-06-25 04:50:57 Why does pg_standby require libpq.so.5?