From: Tom Lane <tgl@sss.pgh.pa.us>
To: Victor Spirin <v.spirin@postgrespro.ru>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Sometimes the output to the stdout in Windows disappears
Date: Sun, 13 Sep 2020 14:37:08 -0400
Message-ID: <855416.1600022228@sss.pgh.pa.us> (raw)
In-Reply-To: <b92a7e09-9a60-d76b-e226-7e191fdc6f34@postgrespro.ru>
References: <ac976d8c-03df-d6b8-025c-15a2de8d9af1@postgrespro.ru>
<4124040.1598898684@sss.pgh.pa.us>
<b92a7e09-9a60-d76b-e226-7e191fdc6f34@postgrespro.ru>
I happened to try googling for other similar reports, and I found
a very interesting recent thread here:
https://github.com/nodejs/node/issues/33166
It might not have the same underlying cause, of course, but it sure
sounds familiar. If Node.js are really seeing the same effect,
that would point to an underlying Windows bug rather than anything
Postgres is doing wrong.
It doesn't look like the Node.js crew got any closer to
understanding the issue than we have, unfortunately. They made
their problem mostly go away by reverting a seemingly-unrelated
patch. But I can't help thinking that it's a timing-related bug,
and that patch was just unlucky enough to change the timing of
their tests so that they saw the failure frequently.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, v.spirin@postgrespro.ru, pgsql-hackers@lists.postgresql.org
Subject: Re: Sometimes the output to the stdout in Windows disappears
In-Reply-To: <855416.1600022228@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox