From: Robert Haas <robertmhaas@gmail.com>
To: Kevin Grittner <kgrittn@gmail.com>
Cc: xen-devel@lists.xenproject.org,
Alvaro Herrera <alvherre@2ndquadrant.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Thomas Munro <thomas.munro@enterprisedb.com>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] [OSSTEST PATCH 0/1] PostgreSQL db: Retry on constraint violation [and 2 more messages]
Date: Wed, 14 Dec 2016 09:42:48 -0500 [thread overview]
Message-ID: <CA+TgmoaM0bqWnXzvvfKvS=orTsOednuUbWC2b8csUmf_=Eii2w__6194.64536798677$1481726634$gmane$org@mail.gmail.com> (raw)
In-Reply-To: <CACjxUsM_GXTFwMGRhDKCUCxeSqk4jrhRM7aMt7QRoY5mPegbzg@mail.gmail.com>
On Wed, Dec 14, 2016 at 9:40 AM, Kevin Grittner <kgrittn@gmail.com> wrote:
> On Wed, Dec 14, 2016 at 8:27 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>> But even after that fix, at the least, you'll still be able to
>> demonstrate the same problem by trapping serialization_failure rather
>> than unique_constraint.
>
> I hope not; the "doomed" flag associated with a serializable
> transaction should cause another attempt to cancel the transaction
> at every subsequent opportunity, including commit. While we're
> digging into bugs in this area it wouldn't hurt (as I said in my
> prior post) to confirm that this is being handled everywhere it
> should be, but I'd be kinda surprised if it wasn't.
Oh, hmm. So you're saying that if I begin a subtransaction, read some
data that causes a serialization anomaly, and then rollback the
subtransaction, my toplevel transaction is now doomed? If so, then
isn't that a counterexample to my proposition that a read-only
transaction can't be cancelled at commit time?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-12-14 14:42 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1481307991-16971-1-git-send-email-ian.jackson@eu.citrix.com>
2016-12-09 18:26 ` [OSSTEST PATCH 1/1] PostgreSQL db: Retry transactions on constraint failures Ian Jackson
2016-12-09 22:37 ` [HACKERS] [OSSTEST PATCH 0/1] PostgreSQL db: Retry on constraint violation Kevin Grittner
[not found] ` <CACjxUsMsHxZ_SrWw7bdCT1Kn8E9mtA1TvhAEbTt-L9AWKKZLCg@mail.gmail.com>
2016-12-12 14:45 ` Ian Jackson
[not found] ` <22606.47105.549023.301281@mariner.uk.xensource.com>
2016-12-12 18:32 ` Kevin Grittner
[not found] ` <CACjxUsMSyhmUStWshxMeAGN7r2YHp1cTSMVPSwDCeVJD-aR6ag@mail.gmail.com>
2016-12-12 19:06 ` Kevin Grittner
[not found] ` <CACjxUsNKtNVhX6EoxY9FjS7N1aJ=inopGT0EqV_yKF6oup0p_g@mail.gmail.com>
2016-12-12 21:47 ` Kevin Grittner
[not found] ` <CACjxUsM3SbYPwPi8K5YJ+w016-GV2RT3mDFHqKAz8Ris+x2vCw@mail.gmail.com>
2016-12-12 22:46 ` Thomas Munro
[not found] ` <CAEepm=3Su08X4tTCUMjpxWAbDWbRhKrdw-hQqSmuhTuzYrytew@mail.gmail.com>
2016-12-13 11:30 ` [HACKERS] [OSSTEST PATCH 0/1] PostgreSQL db: Retry on constraint violation [and 2 more messages] Ian Jackson
[not found] ` <22607.56276.807567.924144@mariner.uk.xensource.com>
2016-12-13 14:22 ` Kevin Grittner
[not found] ` <CACjxUsO+ztVVwxLQ9gdAapn3bqz+1x7m-D8-T8d1Z2aNs0qVfQ@mail.gmail.com>
2016-12-13 15:50 ` Ian Jackson
[not found] ` <22608.6345.97849.783099@mariner.uk.xensource.com>
2016-12-13 16:43 ` Kevin Grittner
[not found] ` <CACjxUsNaAdSDKc_p4S52L3p6r6_7F1Nb+viKaCLFVCY=tYdCTg@mail.gmail.com>
2016-12-13 18:00 ` Ian Jackson
[not found] ` <22608.14118.291149.821376@mariner.uk.xensource.com>
2016-12-13 19:19 ` Kevin Grittner
2016-12-14 6:44 ` Robert Haas
[not found] ` <CA+TgmoZ4MH1tSLGZy7gQFpVh3udsucxqvqc0rF8zHqX8aXmRwQ@mail.gmail.com>
2016-12-14 14:05 ` Alvaro Herrera
2016-12-14 14:26 ` Kevin Grittner
[not found] ` <20161214140539.hotxjeoshju2m7zw@alvherre.pgsql>
2016-12-14 14:27 ` Robert Haas
[not found] ` <CA+TgmoZO+N=ATeWD1fZ4rKngPSOu+EQrTGt_7vtVFMAWVogLOA@mail.gmail.com>
2016-12-14 14:40 ` Kevin Grittner
[not found] ` <CACjxUsM_GXTFwMGRhDKCUCxeSqk4jrhRM7aMt7QRoY5mPegbzg@mail.gmail.com>
2016-12-14 14:42 ` Robert Haas [this message]
2016-12-14 16:20 ` [HACKERS] [OSSTEST PATCH 0/1] PostgreSQL db: Retry on constraint violation [and 2 more messages] [and 1 " Ian Jackson
[not found] ` <CACjxUsNum7KFyAoe0THB2_qGUMsW9AhwRZ8zANnj_Q8spD8=SA@mail.gmail.com>
2016-12-14 14:38 ` [HACKERS] [OSSTEST PATCH 0/1] PostgreSQL db: Retry on constraint violation [and 2 " Robert Haas
[not found] ` <CA+TgmoaZ2CHBVMWRUd=-M6n9iX_4xezNSxHTHGRRmsABVGi4Aw@mail.gmail.com>
2016-12-14 15:00 ` Kevin Grittner
[not found] ` <22609.29020.794032.389420@mariner.uk.xensource.com>
2016-12-14 17:01 ` [HACKERS] [OSSTEST PATCH 0/1] PostgreSQL db: Retry on constraint violation [and 2 more messages] [and 1 " Kevin Grittner
[not found] ` <CACjxUsNRtRSiEcuz5mCsYzNH+62=ZH5j-j=a-iRm6ri-mnMETQ@mail.gmail.com>
2016-12-14 17:12 ` Ian Jackson
[not found] ` <22609.32147.935746.463570@mariner.uk.xensource.com>
2016-12-14 21:13 ` Kevin Grittner
[not found] ` <CACjxUsO2cO70FV2xueUd-cP20XeYotWAxbMBUGTRFsCtO7JHGg@mail.gmail.com>
2016-12-15 12:09 ` Ian Jackson
[not found] ` <22610.34816.412309.196179@mariner.uk.xensource.com>
2016-12-15 14:01 ` Kevin Grittner
[not found] ` <CACjxUsOtSbArs+tnx2rgK37BUANBaCb4oqvdnPaFxU4Oc7FSKw@mail.gmail.com>
2016-12-15 15:53 ` Ian Jackson
[not found] ` <22610.48273.860663.838783@mariner.uk.xensource.com>
2016-12-15 16:35 ` Kevin Grittner
2016-12-16 14:24 ` Robert Haas
[not found] ` <CA+TgmoanO-0e=R3315+wkDw1gG3sXJFhZfG_9-3o4rp=pL-i=g@mail.gmail.com>
2016-12-16 14:39 ` Kevin Grittner
[not found] ` <CACjxUsM2XiWp6GH33M7B+CHEq-s6=traJ5+rr5W4rp==AwyZjg@mail.gmail.com>
2016-12-16 15:00 ` Robert Haas
[not found] ` <CA+TgmoaN0=pEUz_00wY2+tOGiiYOba7kR59HwG8EK0Xbr_HCCQ@mail.gmail.com>
2016-12-16 15:51 ` Kevin Grittner
2016-12-14 17:14 ` Robert Haas
2016-12-14 1:44 ` [HACKERS] [OSSTEST PATCH 0/1] PostgreSQL db: Retry on constraint violation Kevin Grittner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+TgmoaM0bqWnXzvvfKvS=orTsOednuUbWC2b8csUmf_=Eii2w__6194.64536798677$1481726634$gmane$org@mail.gmail.com' \
--to=robertmhaas@gmail.com \
--cc=alvherre@2ndquadrant.com \
--cc=ian.jackson@eu.citrix.com \
--cc=kgrittn@gmail.com \
--cc=pgsql-hackers@postgresql.org \
--cc=thomas.munro@enterprisedb.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.