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

Re: Runtime SHAREDIR for testing CREATE EXTENSION

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-24 16:53:12
Message-ID: 21753.1330102392@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Christoph Berg <cb(at)df7cb(dot)de> writes:
> Re: Sandro Santilli 2012-02-22 <20120222101656(dot)GB6125(at)gnash>
>> 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.

> We have the same problem with testing extensions at build-time in the
> Debian packages. The server's SHAREDIR /usr/share/postgresql/... is
> only writable by root, while the build is running as buildd user, so
> there is no way to do "create extension whatimbuildingrightnow" to be
> able to run regression tests, even if this is a cluster I have just
> created with initdb.

This seems like nonsense.  If the build process has installed the
software, you surely have got permissions to write in that directory.
If you haven't installed the software, you need to do testing in a
temporary installation per "make check", and we are able to test
extensions that way too.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2012-02-24 17:02:43
Subject: Re: Format of raw files
Previous:From: Tom LaneDate: 2012-02-24 16:46:19
Subject: Re: Let's drop V2 protocol

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