Re: [HACKERS] TAP tests take a long time - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [HACKERS] TAP tests take a long time
Date
Msg-id 20170412025041.ndlme6fxh64oef6z@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] TAP tests take a long time  (Craig Ringer <craig.ringer@2ndquadrant.com>)
Responses Re: [HACKERS] TAP tests take a long time  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2017-04-12 10:39:22 +0800, Craig Ringer wrote:
> On 12 April 2017 at 08:22, Michael Paquier <michael.paquier@gmail.com> wrote:
> > On Wed, Apr 12, 2017 at 9:12 AM, Craig Ringer
> > <craig.ringer@2ndquadrant.com> wrote:
> >>
> >> We should also have a debug --no-fsync option for initdb, or maybe allow it
> >> to take -o options to pass to child postgres so we can pass fsync=off .
> >
> > That's an idea as well...
> 
> OK, looking at this, initdb already runs postgres -F then does its own
> fsync()s at the end.
> 
> It already has a -N / --no-sync option too. Which is already used by
> PostgresNode.pm . So as much as can be done has already been done
> here.

The time in initdb is largely spent in regprocin and server start/stop,
so that doesn't surprise me.

- Andres



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [HACKERS] TAP tests take a long time
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] TAP tests take a long time