[pgrouting-dev] pgRouting 2.0 Update

Sandro Santilli strk at keybit.net
Mon Mar 18 05:09:48 PDT 2013


On Sun, Mar 17, 2013 at 08:22:04PM -0400, Stephen Woodbridge wrote:
> On 3/17/2013 2:56 PM, Sandro Santilli wrote:

> >Note it'd currently be impossible to test with the "CREATE EXTENTION"
> >mechanism (no way to load an extension from outside the systemwide
> >directory).
> 
> I just read the thread you started on pgsql-hackers about this issue
> last year. It seems that extension are version wide rather than
> database wide, because the current system assume everything is store
> in a versioned directory tree.
> 
> So if you build postgresql from src you can set the PREFIX to
> something like ~/pgN.N which would give us our private version
> install tree, as a regular user so it does not try to overwrite
> system files. 
...
> Any thoughts on this?

Making tests rely on a specific build of PostgreSQL doesn't seem
a good idea to me. I mean, it's the same as NOT providing pre-install
testing, and delegating to the user the installation in a staging
environment for the sole purpose of testing.

I'm not familiar with extensions, but as long as you still need
enabling and disabling scripts, can't you just always _also_ provide
those scripts and use them for setting up the testing database ?

--strk; 


More information about the pgrouting-dev mailing list