Subject: Re: Sometimes the output to the stdout in Windows disappears
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Victor Spirin <v.spirin@postgrespro.ru>,
 pgsql-hackers@lists.postgresql.org
References: <ac976d8c-03df-d6b8-025c-15a2de8d9af1@postgrespro.ru>
 <4124040.1598898684@sss.pgh.pa.us>
 <b92a7e09-9a60-d76b-e226-7e191fdc6f34@postgrespro.ru>
 <855416.1600022228@sss.pgh.pa.us>
 <ee02eaa2-03f7-74ea-bbdf-3196e506bae3@gmail.com>
 <4156857.1602865112@sss.pgh.pa.us>
 <b32688da-fafc-bbf6-b786-2dd7d0a4d578@gmail.com>
 <117919.1602949857@sss.pgh.pa.us> <132799.1602960277@sss.pgh.pa.us>
 <fca9beed-4902-d955-a691-96950fa54eaa@gmail.com>
 <229665.1603044291@sss.pgh.pa.us>
From: Alexander Lakhin <exclusion@gmail.com>
Message-ID: <6480912b-c0e8-c153-a8b1-0d64b16f9cb9@gmail.com>
Date: Sun, 18 Oct 2020 21:30:01 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <229665.1603044291@sss.pgh.pa.us>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Precedence: bulk

18.10.2020 21:04, Tom Lane wrote:
> Alexander Lakhin <exclusion@gmail.com> writes:
>> @@ -0,0 +1 @@
>> +SQL error: descriptor "mydesc" not found on line 31
> does not look like the same kind of failure as what we've been dealing
> with up to now.  So maybe what we've got is that we fixed the stdio
> loss problem, and now the error rate is down to the point where we can
> notice other, even-lower-probability issues.
Yes, in this case stderr is not missing (it's present with the error).
So it's really different case. As is another one:

test connect/test5                ... stderr FAILED      238 ms

diff -w -U3 .../src/interfaces/ecpg/test/expected/connect-test5.stderr
.../src/interfaces/ecpg/test/results/connect-test5.stderr
--- .../src/interfaces/ecpg/test/expected/connect-test5.stderr   
2020-10-13 21:51:14 +0300
+++ .../src/interfaces/ecpg/test/results/connect-test5.stderr   
2020-10-18 20:59:46 +0300
@@ -73,7 +73,9 @@
 [NO_PID]: sqlca: code: -220, state: 08003
 [NO_PID]: ECPGconnect: opening database <DEFAULT> on <DEFAULT> port
<DEFAULT>  for user regress_ecpg_user2
 [NO_PID]: sqlca: code: 0, state: 00000
-[NO_PID]: ECPGconnect: could not open database: FATAL:  database
"regress_ecpg_user2" does not exist
+[NO_PID]: ECPGconnect: could not open database: server closed the
connection unexpectedly
+    This probably means the server terminated abnormally
+    before or while processing the request.

and the server.log:
2020-10-18 20:59:45.731 MSK client backend[1380] ecpg/connect-test4
LOG:  could not receive data from client: An existing connection was
forcibly closed by the remote host.
   
2020-10-18 20:59:45.898 MSK client backend[2884] [unknown] FATAL: 
database "regress_ecpg_user2" does not exist
2020-10-18 20:59:45.992 MSK client backend[1640] [unknown] FATAL: 
database "regress_ecpg_user2" does not exist

I just wanted to inform that the ECPG-test failures can still persist in
the buildfarm, unfortunately.

Best regards,
Alexander