Date: Wed, 11 Jul 2018 13:49:06 -0400
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Marina Polyakova <m.polyakova@postgrespro.ru>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>, pgsql-hackers@postgresql.org,
	Ildus Kurbangaliev <i.kurbangaliev@postgrespro.ru>,
	Teodor Sigaev <teodor@sigaev.ru>
Subject: Re: [HACKERS] WIP Patch: Pgbench Serialization and deadlock errors
Message-ID: <20180711174906.oscbjjivg6gc2riu@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <976a25a46420c93866ada4051976b1be@postgrespro.ru>
User-Agent: NeoMutt/20170306-137-4415bd-dirty (1.8.0)
Precedence: bulk

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