Re: [HACKERS] Cutting initdb's runtime (Perl question embedded)
| От | Andrew Dunstan | 
|---|---|
| Тема | Re: [HACKERS] Cutting initdb's runtime (Perl question embedded) | 
| Дата | |
| Msg-id | 4dda7d5c-b7f7-f89a-792e-a52e72be71d3@2ndQuadrant.com обсуждение исходный текст  | 
		
| Ответ на | Re: [HACKERS] Cutting initdb's runtime (Perl question embedded) (Tom Lane <tgl@sss.pgh.pa.us>) | 
| Ответы | 
                	
            		Re: [HACKERS] Cutting initdb's runtime (Perl question embedded)
            		
            		 Re: [HACKERS] Cutting initdb's runtime (Perl question embedded)  | 
		
| Список | pgsql-hackers | 
On 04/15/2017 12:13 PM, Tom Lane wrote:
> Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
>> What I had in mind was the attached plus roughly this in the buildfarm
>> client:
>>     $ENV{TZ} ||= 'US/Eastern';
>> or whatever zone we choose to use.
> How about letting the first "make check" run with whatever is in the
> environment, and then forcing TZ to become set (much as above) for
> all the remaining tests?  I'm afraid what you've got here might
> encourage a certain sameness of the test environments.
>
>             
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.
cheers
andrew
-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
		
	В списке pgsql-hackers по дате отправления: