Re: pgbench vs. SERIALIZABLE

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgbench vs. SERIALIZABLE
Date: 2013-05-18 22:03:31
Message-ID: alpine.DEB.2.02.1305182259550.1473@localhost6.localdomain6
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> My thinking is that what pgbench should do is:
> * track an error count
> * if it finds an error, don't increment the transaction count, but do
> increment the error count.
> * then continue to the next transaction.
>
> Does that seem like the right approach?

Could it retry the *same* transaction instead of the next one?

Should it give up trying under some conditions, say there are more errors
than transactions?

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Tiikkaja 2013-05-19 00:08:27 Re: pgbench vs. SERIALIZABLE
Previous Message Josh Berkus 2013-05-18 21:34:11 pgbench vs. SERIALIZABLE