pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Lakhin <exclusion@gmail.com>
Cc: 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, 18 Oct 2020 14:04:51 -0400
Message-ID: <229665.1603044291@sss.pgh.pa.us> (raw)
In-Reply-To: <fca9beed-4902-d955-a691-96950fa54eaa@gmail.com>
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>

Alexander Lakhin <exclusion@gmail.com> writes:
> With the fix all the 200 iterations passed as expected.
> Then I ran the loop again just to be sure and got:
> test thread/descriptor            ... stderr FAILED       81 ms
> iteration 124 failed.

Sigh ... still, this:

> diff -w -U3
> .../src/interfaces/ecpg/test/expected/thread-descriptor.stderr
> .../src/interfaces/ecpg/test/results/thread-descriptor.stderr
> --- .../src/interfaces/ecpg/test/expected/thread-descriptor.stderr   
> 2019-12-04 16:05:46 +0300
> +++ .../src/interfaces/ecpg/test/results/thread-descriptor.stderr   
> 2020-10-18 20:20:27 +0300
> @@ -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.

			regards, tom lane





view thread (16+ messages)  latest in thread

Message-ID: <229665.1603044291@sss.pgh.pa.us>
Permalink:  ../229665.1603044291@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/229665.1603044291@sss.pgh.pa.us

 · 

reply
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, exclusion@gmail.com, v.spirin@postgrespro.ru, pgsql-hackers@lists.postgresql.org
  Subject: Re: Sometimes the output to the stdout in Windows disappears
  In-Reply-To: <229665.1603044291@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