From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Runtime SHAREDIR for testing CREATE EXTENSION |
Date: | 2012-02-21 21:34:42 |
Message-ID: | m2pqd77tvx.fsf@2ndQuadrant.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Sandro Santilli <strk(at)keybit(dot)net> writes:
> On Tue, Feb 21, 2012 at 10:21:17AM -0500, Tom Lane wrote:
>> Sandro Santilli <strk(at)keybit(dot)net> writes:
>> > I'm trying to understand what options I have to test "CREATE EXTENSION"
>> > w/out installing the extension files in their final destination.
>>
>> There aren't any. Generally speaking, if you want to be testing an
>> extension, you should be doing it in a test installation anyway;
>> so I don't see what's the objection to sticking the files into the
>> installation's real SHAREDIR.
>
> We do a staged installation of the extension library and scripts
> in an ad-hoc dir which does not match the built-in SHAREDIR of PostgreSQL.
>
> It works fine for testing the extension directly sourcing the scripts.
> It's only "CREATE EXTENSION" that doesn't play nicely with that setup.
Please see the "inline extension" thread where answers to your problem
have been discussed.
https://commitfest.postgresql.org/action/patch_view?id=746
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2012-02-21 21:44:04 | Re: Displaying accumulated autovacuum cost |
Previous Message | Tom Lane | 2012-02-21 20:51:07 | Re: Re: [COMMITTERS] pgsql: Correctly initialise shared recoveryLastRecPtr in recovery. |