Skip site navigation (1) Skip section navigation (2)


From: Sandro Santilli <strk(at)keybit(dot)net>
To: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Runtime SHAREDIR for testing CREATE EXTENSION
Date: 2012-02-22 10:16:56
Message-ID: 20120222101656.GB6125@gnash (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Tue, Feb 21, 2012 at 10:34:42PM +0100, Dimitri Fontaine wrote:
> 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.

I'm not really looking for "inline extensions".
I do want to install the extension objects somewhere, just NOT
in the PostgreSQL builtin SHAREDIR but in an arbitrary staging
directory to use for QA the extension before distribution.


  |   __/  |    Delivering high quality PostGIS 2.0 !
  |  / 2.0 |

In response to


pgsql-hackers by date

Next:From: Greg SmithDate: 2012-02-22 11:53:49
Subject: pg_test_timing tool for EXPLAIN ANALYZE overhead
Previous:From: Dimitri FontaineDate: 2012-02-22 10:07:16
Subject: Extensions default full version (was: Displaying accumulated autovacuum cost)

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group