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

From Fabien COELHO
Subject Re: [HACKERS] WIP Patch: Pgbench Serialization and deadlock errors
Date
Msg-id alpine.DEB.2.20.1803251417220.8109@lancre
Whole thread Raw
In response to Re: [HACKERS] WIP Patch: Pgbench Serialization and deadlock errors  (Teodor Sigaev <teodor@sigaev.ru>)
Responses Re: [HACKERS] WIP Patch: Pgbench Serialization and deadlock errors
List 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.

Yep.

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 
already.

-- 
Fabien.


pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: Re: WIP: a way forward on bootstrap data
Next
From: Michael Paquier
Date:
Subject: Simplify final sync in pg_rewind's target folder and add --no-sync