From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
        Andreas Karlsson <andreas@proxel.se>,
        Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org
Subject: Re: Cutting initdb's runtime (Perl question embedded)
In-reply-to: <4dda7d5c-b7f7-f89a-792e-a52e72be71d3@2ndQuadrant.com>
References: <20170415154440.3eg3dltxs5zybmv2@alvherre.pgsql>
 <389c14b5-3678-e617-450f-07bf29197249@2ndQuadrant.com>
 <29572.1492272795@sss.pgh.pa.us>
 <4dda7d5c-b7f7-f89a-792e-a52e72be71d3@2ndQuadrant.com>
Comments: In-reply-to Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
	message dated "Sat, 15 Apr 2017 12:33:54 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8601.1492280001.1@sss.pgh.pa.us>
Date: Sat, 15 Apr 2017 14:13:21 -0400
Message-ID: <8602.1492280001@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
> Sure. Just means putting this code a bit later in the file. "make check"
> is only one initdb, so it won't cost much. I'm still inclined to force a
> TAP test for initdb with no TZ set, though.

I'd like that to be an additional tweak for some existing test case
rather than expending a whole initdb run just for that --- but otherwise,
no objection.

			regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers