On 02/24/2012 06:31 PM, Daniel Farina wrote:
> On Fri, Feb 24, 2012 at 10:21 AM, Peter Eisentraut<peter_e@gmx.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@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