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

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Teodor Sigaev <teodor(at)sigaev(dot)ru>
Cc: Marina Polyakova <m(dot)polyakova(at)postgrespro(dot)ru>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] WIP Patch: Pgbench Serialization and deadlock errors
Date: 2018-03-25 12:23:21
Message-ID: alpine.DEB.2.20.1803251417220.8109@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> Hm, I took a look on both thread about patch and it seems to me now it's
> overcomplicated. With recently committed enhancements of pgbench (\if,
> \when) it becomes close to impossible to retry transation in case of
> failure. So, initial approach just to rollback such transaction looks
> more attractive.


I think that the best approach for now is simply to reset (command zero,
random generator) and start over the whole script, without attempting to
be more intelligent. The limitations should be clearly documented (one
transaction per script), though. That would be a significant enhancement


In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-03-25 12:26:07 Simplify final sync in pg_rewind's target folder and add --no-sync
Previous Message John Naylor 2018-03-25 11:34:25 Re: WIP: a way forward on bootstrap data