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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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;
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-02-21 18:21:31 | Re: Unfamous 'could not read block ... in file "...": read only 0 of 8192 bytes' again |
Previous Message | Jan Urbański | 2012-02-21 17:28:29 | Re: Potential reference miscounts and segfaults in plpython.c |