From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
---|---|
To: | 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-23 14:15:17 |
Message-ID: | 72ca61a8-b515-1bac-b082-b77952c78b64@sigaev.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I suggest a patch where pgbench client sessions are not disconnected because of
> serialization or deadlock failures and these failures are mentioned in reports.
> In details:
> - transaction with one of these failures continue run normally, but its result
> is rolled back;
> - if there were these failures during script execution this "transaction" is marked
> appropriately in logs;
> - numbers of "transactions" with these failures are printed in progress, in
> aggregation logs and in the end with other results (all and for each script);
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.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-03-23 14:23:58 | Re: Odd procedure resolution |
Previous Message | Andrey Borodin | 2018-03-23 14:13:09 | Re: [HACKERS] A design for amcheck heapam verification |