| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "Patrick Earl" <patearl(at)patearl(dot)net>, "<pgsql-hackers(at)postgresql(dot)org>" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Select For Update and Left Outer Join |
| Date: | 2011-07-11 17:09:41 |
| Message-ID: | 4E1AE805020000250003F1BA@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> I'm wondering if it wouldn't make sense to dodge all that by
> having SELECT FOR UPDATE simple *do* a no-op UPDATE RETURNING.
Hmm.
Patrick, would it be possible to change the PostgreSQL code for
Hibernate to use UPDATE RETURNING instead of SELECT FOR UPDATE?
That might allow portable Hibernate applications to work properly
with recent PostgreSQL versions without going to SERIALIZABLE
transactions.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2011-07-11 17:19:53 | Re: Full GUID support |
| Previous Message | Tom Lane | 2011-07-11 16:56:05 | Re: Launching debugger on self on SIGSEGV |