Re: Unportable use of select for timeouts in PostgresNode.pm

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unportable use of select for timeouts in PostgresNode.pm
Date: 2017-07-17 15:40:28
Message-ID: 6062.1500306028@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
> 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.
> + select undef, 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.

Ugh.

> 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.

WFM. Thanks for taking care of it.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-07-17 15:46:12 Why have we got both largeobject and large_object test files?
Previous Message Michael Paquier 2017-07-17 15:37:54 Re: Something for the TODO list: deprecating abstime and friends