Re: Maybe BF "timedout" failures are the client script's fault? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Maybe BF "timedout" failures are the client script's fault?
Date
Msg-id 2545896.1768063051@sss.pgh.pa.us
Whole thread Raw
In response to Re: Maybe BF "timedout" failures are the client script's fault?  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> The patch seems reasonable on its face, but I doubt it's the issue. 
> Rather I think what's happening here is that a test is hanging silently 
> and lastcommand.log's mtime doesn't get updated, causing a misreporting 
> of the run duration. So in addition to the above I have added some code 
> to update that timestamp if the file exists (which should only be the 
> case with a timeout).

Sounds reasonable.  Thanks!

            regards, tom lane



pgsql-hackers by date:

Previous
From: Marco Matteucci
Date:
Subject: [RFC] SLIM Data Type - Compact JSON Alternative (17-62% smaller)
Next
From: Tom Lane
Date:
Subject: Re: JumbleQuery ma treat different GROUP BY expr as the same