Re: Maybe BF "timedout" failures are the client script's fault?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: michael(dot)banck(at)credativ(dot)de, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Maybe BF "timedout" failures are the client script's fault?
Date: 2026-01-10 16:37:31
Message-ID: 2545896.1768063051@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)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

In response to

Browse pgsql-hackers by date

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