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

Re: Runtime SHAREDIR for testing CREATE EXTENSION

From: Sandro Santilli <strk(at)keybit(dot)net>
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 17:42:42
Message-ID: 20120221174242.GL1546@gnash (view raw or flat)
Thread:
Lists: pgsql-hackers
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.

--strk; 

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2012-02-21 18:21:31
Subject: Re: Unfamous 'could not read block ... in file "...": read only 0 of 8192 bytes' again
Previous:From: Jan UrbaƄskiDate: 2012-02-21 17:28:29
Subject: Re: Potential reference miscounts and segfaults in plpython.c

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