Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors

From: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: ishii(at)sraoss(dot)co(dot)jp, nagata(at)sraoss(dot)co(dot)jp, coelho(at)cri(dot)ensmp(dot)fr, thomas(dot)munro(at)gmail(dot)com, m(dot)polyakova(at)postgrespro(dot)ru, alvherre(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org, teodor(at)sigaev(dot)ru
Subject: Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors
Date: 2022-03-24 23:50:44
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

>> My machine (Ubuntu 20) did not complain either. Maybe perl version
>> difference? Any way, the fix pushed. Let's see how prairiedog feels.
> Still not happy. After some digging in man pages, I believe the
> problem is that its old version of Perl does not understand "\gN"
> backreferences. Is there a good reason to be using that rather
> than the traditional "\N" backref notation?

I don't see a reason to use "\gN" either. Actually after applying
attached patch, my machine is still happy with pgbench test.

Tatsuo Ishii
SRA OSS, Inc. Japan

Attachment Content-Type Size
fix_pgbench_test_v2.patch text/x-patch 583 bytes

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-03-25 00:02:34 Re: Race conditions in
Previous Message Chapman Flack 2022-03-24 23:42:37 Re: Re: pg_dump new feature: exporting functions only. Bad or good idea ?