[HACKERS] Unportable use of select for timeouts in PostgresNode.pm - Mailing list pgsql-hackers

From Andrew Dunstan
Subject [HACKERS] Unportable use of select for timeouts in PostgresNode.pm
Date
Msg-id 186943e0-3405-978d-b19d-9d3335427c86@2ndQuadrant.com
Whole thread Raw
Responses Re: [HACKERS] Unportable use of select for timeouts in PostgresNode.pm
Re: [HACKERS] Unportable use of select for timeouts in PostgresNode.pm
List pgsql-hackers
I've been trying to get to the bottom of a nasty hang in buildfarm
member jacana when running the pg_ctl TAP test. This test used to work,
and was last known to work on June 22nd.

My attention has become focussed on this change in commit de3de0afd:
   -       # Wait a second before retrying.   -       sleep 1;   +       # Wait 0.1 second before retrying.   +
selectundef, undef, undef, 0.1;
 

This is a usage that is known not to work in Windows - IIRC we
eliminated such calls from our C programs at the time of the Windows
port - and it seems to me very likely to be the cause of the hang.
Instead I think we should use the usleep() function from the standard
(from 5.8) Perl module Time::HiRes, as recommended in the Perl docs for
the sleep() function for situations where you need finer grained
timeouts. I have verified that this works on jacana and friends.

Unless I hear objections I'll prepare a patch along those lines.


cheers


andrew

-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] pg_restore failed for foreign key constraint
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] segfault in HEAD when too many nested functions call