pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: nagata@sraoss.co.jp
Cc: coelho@cri.ensmp.fr
Cc: thomas.munro@gmail.com
Cc: m.polyakova@postgrespro.ru
Cc: alvherre@2ndquadrant.com
Cc: pgsql-hackers@postgresql.org
Cc: teodor@sigaev.ru
Subject: Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors
Date: Wed, 23 Mar 2022 14:26:54 -0400
Message-ID: <2775989.1648060014@sss.pgh.pa.us> (raw)
In-Reply-To: <20220323.190809.88053056758099179.t-ishii@sranhm.sra.co.jp>
References: <20220322090815.2b59ff5139c666f25312c337@sraoss.co.jp>
	<20220322172714.7ac718269598b7d52b009dd7@sraoss.co.jp>
	<20220322.184415.118632931744953435.t-ishii@sranhm.sra.co.jp>
	<20220323.190809.88053056758099179.t-ishii@sranhm.sra.co.jp>

Tatsuo Ishii <ishii@sraoss.co.jp> writes:
> The patch Pushed. Thank you!

My hoary animal prairiedog doesn't like this [1]:

#   Failed test 'concurrent update with retrying stderr /(?s-xim:client (0|1) got an error in command 3 \\(SQL\\) of script 0; ERROR:  could not serialize access due to concurrent update\\b.*\\g1)/'
#   at t/001_pgbench_with_server.pl line 1229.
#                   'pgbench: pghost: /tmp/nhghgwAoki pgport: 58259 nclients: 2 nxacts: 1 dbName: postgres
...
# pgbench: client 0 got an error in command 3 (SQL) of script 0; ERROR:  could not serialize access due to concurrent update
...
# '
#     doesn't match '(?s-xim:client (0|1) got an error in command 3 \\(SQL\\) of script 0; ERROR:  could not serialize access due to concurrent update\\b.*\\g1)'
# Looks like you failed 1 test of 425.

I'm not sure what the "\\b.*\\g1" part of this regex is meant to
accomplish, but it seems to be assuming more than it should
about the output format of TAP messages.

			regards, tom lane

[1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prairiedog&dt=2022-03-23%2013%3A21%3A44





view thread (82+ messages)  latest in thread

Message-ID: <2775989.1648060014@sss.pgh.pa.us>
Permalink:  ../2775989.1648060014@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2775989.1648060014@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, ishii@sraoss.co.jp, nagata@sraoss.co.jp, coelho@cri.ensmp.fr, thomas.munro@gmail.com, m.polyakova@postgrespro.ru, alvherre@2ndquadrant.com, teodor@sigaev.ru
  Subject: Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors
  In-Reply-To: <2775989.1648060014@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