Re: Runtime SHAREDIR for testing CREATE EXTENSION

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Daniel Farina <daniel(at)heroku(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Sandro Santilli <strk(at)keybit(dot)net>, Christoph Berg <cb(at)df7cb(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Runtime SHAREDIR for testing CREATE EXTENSION
Date: 2012-02-25 02:31:50
Message-ID: 4F484816.10909@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 02/24/2012 06:31 PM, Daniel Farina wrote:
> On Fri, Feb 24, 2012 at 10:21 AM, Peter Eisentraut<peter_e(at)gmx(dot)net> wrote:
>> On fre, 2012-02-24 at 17:26 +0100, Sandro Santilli wrote:
>>> We don't initdb with PostGIS regression testing framework
>>> but I've considered doing it for this specific case and it stroke me
>>> that even then we couldn't control SHAREDIR.
>> I would always create a new instance using initdb for test runs. It's
>> easy and avoids all these problems.
> Having been in this position once before in a different but similar
> situation, there's one big caveat: initdb is *really* slow, so it is
> really painful for people who write Postgres-linked code that is
> compiled separately, whereby the initdb binary is stable. The
> frustration is not unlike when I have to run ./configure, except I had
> to do it all the time, every time.

Really? Here's what I just got on a severely under-resourced SL6 VM:

[andrew(at)xena ~]$ time /usr/pgsql-9.1/bin/initdb -A ident foo > /dev/null

real 0m1.441s
user 0m1.131s
sys 0m0.309s

1.5s doesn't seem terribly slow.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Farina 2012-02-25 02:43:07 Re: Runtime SHAREDIR for testing CREATE EXTENSION
Previous Message Noah Misch 2012-02-25 02:01:35 Re: [PATCH] Support for foreign keys with arrays