Re: BackgroundPsql swallowing errors on windows

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Noah Misch <noah@leadboat.com>

Cc: Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org

Date: 2025-02-17T00:50:18Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

tests: BackgroundPsql: Fix potential for lost errors on windows
- bb2bf22761e1 13.21 landed
- c21ebcca7965 14.18 landed
- 70b650d18553 15.13 landed
- 4c9397c374d9 16.9 landed
- f61769adaa62 17.5 landed
- 8b886a4e3488 18.0 landed
Improve handling of empty query results in BackgroundPsql::query()
- 70291a3c66ec 18.0 cited
Extend Cluster.pm's background_psql() to be able to start asynchronously
- ba08edb06545 18.0 cited

Noah Misch <noah@leadboat.com> writes:
> On Sun, Feb 16, 2025 at 06:18:44PM -0500, Tom Lane wrote:
>> I think that
>> IPC::Run may be screwing up here, because I have seen non-Windows
>> CI failures that look like it didn't read all the stderr output.
>> For example, this pgbench test failure on macOS from [1]:

> https://github.com/cpan-authors/IPC-Run/commit/2128df3bbcac7e733ac46302c4b1371ffb88fe14
> fixed that one.

Ah.  Do we know whether that fix has made it into our CI images?
(Or anywhere else, for that matter?)

			regards, tom lane