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

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Marina Polyakova <m(dot)polyakova(at)postgrespro(dot)ru>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, Ildus Kurbangaliev <i(dot)kurbangaliev(at)postgrespro(dot)ru>, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Subject: Re: [HACKERS] WIP Patch: Pgbench Serialization and deadlock errors
Date: 2018-07-12 16:04:21
Message-ID: alpine.DEB.2.21.1807121801250.27883@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

>> The point is to avoid building the message with dynamic allocation and so
>> if in the end it is not used.
> Ok! About avoidance - I'm afraid there's one more piece of debugging code
> with the same problem:

Indeed. I'd like to avoid all instances, so that PQExpBufferData is not
needed anywhere, if possible. If not possible, then too bad, but I'd
prefer to make do with formatted prints only, for simplicity.


In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey Borodin 2018-07-12 16:06:38 Re: GiST VACUUM
Previous Message Fabien COELHO 2018-07-12 16:00:14 Re: [HACKERS] Re: [COMMITTERS] pgsql: Remove pgbench "progress" test pending solution of its timing is (fwd)