Re: [HACKERS] WIP Patch: Pgbench Serialization and deadlock errors - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [HACKERS] WIP Patch: Pgbench Serialization and deadlock errors
Date
Msg-id 20180711174906.oscbjjivg6gc2riu@alvherre.pgsql
Whole thread Raw
In response to Re: [HACKERS] WIP Patch: Pgbench Serialization and deadlock errors  (Marina Polyakova <m.polyakova@postgrespro.ru>)
Responses Re: [HACKERS] WIP Patch: Pgbench Serialization and deadlock errors  (Marina Polyakova <m.polyakova@postgrespro.ru>)
List pgsql-hackers
On 2018-Jul-11, Marina Polyakova wrote:

> can we try something like this?
> 
> PGBENCH_ERROR_START(DEBUG_FAIL)
> {
>     PGBENCH_ERROR("client %d repeats the failed transaction (try %d",
>                   st->id, st->retries + 1);
>     if (max_tries)
>         PGBENCH_ERROR("/%d", max_tries);
>     if (latency_limit)
>     {
>         PGBENCH_ERROR(", %.3f%% of the maximum time of tries was used",
>                       getLatencyUsed(st, &now));
>     }
>     PGBENCH_ERROR(")\n");
> }
> PGBENCH_ERROR_END();

I didn't quite understand what these PGBENCH_ERROR() functions/macros
are supposed to do.  Care to explain?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: In pageinspect, perform clean-up after testing gin-related functions
Next
From: Heikki Linnakangas
Date:
Subject: Re: [PATCH] Add missing type conversion functions for PL/Python