diff options
author | Kevin Grittner <kgrittn@postgresql.org> | 2016-12-13 19:05:12 -0600 |
---|---|---|
committer | Kevin Grittner <kgrittn@postgresql.org> | 2016-12-13 19:05:12 -0600 |
commit | 4b9d466c14083003bd80e1ce02e617b2b92df7fe (patch) | |
tree | 2bc77f27c4944db1609f2ca7abd16b5fc6eb3964 /src/tutorial | |
parent | fb12471ebec11417d49e705e8cb77baaa53f0473 (diff) |
Back-patch fcff8a575198478023ada8a48e13b50f70054766 as a bug fix.
When there is both a serialization failure and a unique violation,
throw the former rather than the latter. When initially pushed,
this was viewed as a feature to assist application framework
developers, so that they could more accurately determine when to
retry a failed transaction, but a test case presented by Ian
Jackson has shown that this patch can prevent serialization
anomalies in some cases where a unique violation is caught within a
subtransaction, the work of that subtransaction is discarded, and
no error is thrown. That makes this a bug fix, so it is being
back-patched to all supported branches where it is not already
present (i.e., 9.2 to 9.5).
Discussion: https://postgr.es/m/1481307991-16971-1-git-send-email-ian.jackson@eu.citrix.com
Discussion: https://postgr.es/m/22607.56276.807567.924144@mariner.uk.xensource.com
Diffstat (limited to 'src/tutorial')
0 files changed, 0 insertions, 0 deletions