From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Christoph Berg <cb(at)df7cb(dot)de> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Runtime SHAREDIR for testing CREATE EXTENSION |
Date: | 2012-02-26 15:36:00 |
Message-ID: | 1330270560.32452.32.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On lör, 2012-02-25 at 14:21 +0100, Christoph Berg wrote:
> Well, I'm trying to invoke the extension's "make check" target at
> extension build time. I do have a temporary installation I own
> somehwere in my $HOME, but that is still trying to find extensions in
> /usr/share/postgresql/9.1/extension/*.control, because I am using the
> system's postgresql version. The build process is not running as root,
> so I cannot do an install of the extension to its final location.
> Still it would be nice to run regression tests. All that seems to be
> missing is the ability to put
>
> extension_control_path = /home/buildd/tmp/extension
>
> into the postgresql.conf of the temporary PG installation, or some
> other way like "CREATE EXTENSION foobar WITH CONTROL
> '/home/buildd/...'.
Yeah, of course, the extension path is not related to the data
directory. So we do need some kind of path setting, just like
dynamic_library_path.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2012-02-26 15:39:09 | Re: leakproof |
Previous Message | Pavel Stehule | 2012-02-26 15:04:23 | WARNING: concurrent insert in progress within table "resource" |