Re: Runtime SHAREDIR for testing CREATE EXTENSION - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: Runtime SHAREDIR for testing CREATE EXTENSION
Date
Msg-id m2pqd77tvx.fsf@2ndQuadrant.fr
Whole thread Raw
In response to Re: Runtime SHAREDIR for testing CREATE EXTENSION  (Sandro Santilli <strk@keybit.net>)
Responses Re: Runtime SHAREDIR for testing CREATE EXTENSION  (Sandro Santilli <strk@keybit.net>)
Re: Runtime SHAREDIR for testing CREATE EXTENSION  (Daniel Farina <daniel@heroku.com>)
List pgsql-hackers
Sandro Santilli <strk@keybit.net> writes:
> On Tue, Feb 21, 2012 at 10:21:17AM -0500, Tom Lane wrote:
>> Sandro Santilli <strk@keybit.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Correctly initialise shared recoveryLastRecPtr in recovery.
Next
From: Dimitri Fontaine
Date:
Subject: Re: Displaying accumulated autovacuum cost