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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
Cc: 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 18:02:59
Message-ID: 3028358.1648144979@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> writes:
>> My hoary animal prairiedog doesn't like this [1]:

> 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?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-03-24 18:19:35 Re: [PATCH] Expose port->authn_id to extensions and triggers
Previous Message Robert Haas 2022-03-24 17:55:29 Re: [PATCH] Expose port->authn_id to extensions and triggers