Re: pgbench: using prepared BEGIN statement in a pipeline could cause an error

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: nagata(at)sraoss(dot)co(dot)jp
Cc: daniel(at)yesql(dot)se, coelho(at)cri(dot)ensmp(dot)fr, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pgbench: using prepared BEGIN statement in a pipeline could cause an error
Date: 2022-01-27 08:50:25
Message-ID: 20220127.175025.684118651632935772.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Tue, 16 Nov 2021 02:26:43 +0900, Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp> wrote in
> Thank you for pointing it out!
> I attached the updated patch.

I think we want more elabolative comment for the new place of
preparing as you mentioned in the first mail.

At Fri, 16 Jul 2021 15:30:13 +0900, Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp> wrote in
> One way to avoid these errors is to send Parse messages before
> pipeline mode starts.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2022-01-27 09:40:18 Re: libpq async duplicate error results
Previous Message Anand Sowmithiran 2022-01-27 08:21:10 Re: Output clause for Upsert aka INSERT...ON CONFLICT