| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | Marina Polyakova <m(dot)polyakova(at)postgrespro(dot)ru> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Subject: | Re: WIP Patch: Pgbench Serialization and deadlock errors |
| Date: | 2017-06-16 17:43:15 |
| Message-ID: | CACjxUsMORf0ZgR73C3mQ60wDNbs1B4_V6vDVGJ0MkL=Ej_K1mg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 16, 2017 at 5:31 AM, Marina Polyakova
<m(dot)polyakova(at)postgrespro(dot)ru> wrote:
> And thank you very much for your explanation how and why transactions with
> failures should be retried! I'll try to implement all of it.
To be clear, part of "retrying from the beginning" means that if a
result from one statement is used to determine the content (or
whether to run) a subsequent statement, that first statement must be
run in the new transaction and the results evaluated again to
determine what to use for the later statement. You can't simply
replay the statements that were run during the first try. For
examples, to help get a feel of why that is, see:
https://wiki.postgresql.org/wiki/SSI
--
Kevin Grittner
VMware vCenter Server
https://www.vmware.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2017-06-16 17:44:30 | Re: Preliminary results for proposed new pgindent implementation |
| Previous Message | Tom Lane | 2017-06-16 17:34:01 | Re: Preliminary results for proposed new pgindent implementation |