pg.ddx.io  pgsql-bugs@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: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16685: The ecpg thread/descriptor test fails sometimes on Windows
Date: Sat, 24 Oct 2020 16:41:09 -0400
Message-ID: <390897.1603572069@sss.pgh.pa.us> (raw)
In-Reply-To: <dedbf623-ae82-5635-a639-944395697799@gmail.com>
References: <16685-d6cd241872c101d3@postgresql.org>
	<367782.1603554604@sss.pgh.pa.us>
	<380144.1603558463@sss.pgh.pa.us>
	<dedbf623-ae82-5635-a639-944395697799@gmail.com>

BTW, I searched the buildfarm logs of ECPG failures to see if I could
find anything related to this, and noticed that there were a fair
number of Windows-machine failures in the thread/prep test.  They don't
all look quite alike, but this one is representative (and the most
recent):

sysname|dory
snapshot|2019-04-02 11:20:25
================== pgsql.build/src/interfaces/ecpg/test/regression.diffs ===================
inline patch 1: c:/pgbuildfarm/pgbuildroot/HEAD/pgsql.build/src/interfaces/ecpg/test/results/thread-prep.stderr (+10/-0 lines) download inline-1.patchdiff -w -U3 c:/pgbuildfarm/pgbuildroot/HEAD/pgsql.build/src/interfaces/ecpg/test/expected/thread-prep.stderr c:/pgbuildfarm/pgbuildroot/HEAD/pgsql.build/src/interfaces/ecpg/test/results/thread-prep.stderr --- c:/pgbuildfarm/pgbuildroot/HEAD/pgsql.build/src/interfaces/ecpg/test/expected/thread-prep.stderr 2018-04-20 16:03:08 -0400 +++ c:/pgbuildfarm/pgbuildroot/HEAD/pgsql.build/src/interfaces/ecpg/test/results/thread-prep.stderr 2019-04-02 07:43:27 -0400 @@ -0,0 +1,84 @@ +SQL error: could not connect to database "ecpg1_regression" on line 48 +SQL error: the connection to the server was lost on line 53 +SQL error: the connection to the server was lost on line 52 +SQL error: invalid statement name "i" on line 53 +SQL error: the connection to the server was lost on line 52 +SQL error: invalid statement name "i" on line 53 +SQL error: the connection to the server was lost on line 52 +SQL error: invalid statement name "i" on line 53 +SQL error: the connection to the server was lost on line 52 +SQL error: invalid statement name "i" on line 53
... quite a few repetitions of this ... +SQL error: the connection to the server was lost on line 52 +SQL error: invalid statement name "i" on line 53 +SQL error: invalid statement name "i" on line 55 +SQL error: connection "Connection: 1" does not exist on line 56 I suspect that this might arise from a pthread_once failure associated with the actual_connection_key variable. regards, tom lane

view thread (5+ messages)

Message-ID: <390897.1603572069@sss.pgh.pa.us>
Permalink:  ../390897.1603572069@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/390897.1603572069@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-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, exclusion@gmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #16685: The ecpg thread/descriptor test fails sometimes on Windows
  In-Reply-To: <390897.1603572069@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