Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.postgresql > #113
| Path | csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!news.linkpendium.com!news.linkpendium.com!teleglobe.net!newsgate.cuhk.edu.hk!news.netfront.net!reversiblemaps.ath.cx!not-for-mail |
|---|---|
| From | Jasen Betts <jasen@xnet.co.nz> |
| Newsgroups | comp.databases.postgresql |
| Subject | Re: Deadlock on the same select for update |
| Date | 3 May 2011 08:31:31 GMT |
| Organization | Dis (not Dat) Organisation |
| Lines | 19 |
| Message-ID | <ipoeh3$4l4$1@reversiblemaps.ath.cx> (permalink) |
| References | <f7c3a742-d9c8-4e38-9708-a9f458a36a59@i14g2000yqe.googlegroups.com> <wZq*U2kwt@news.chiark.greenend.org.uk> <pan.2011.02.23.14.34.04@gmail.com> <zUj*3xvwt@news.chiark.greenend.org.uk> <1304409229.248884@proxy.dienste.wien.at> |
| NNTP-Posting-Host | 118.90.133.108 |
| Mime-Version | 1.0 |
| Content-Type | text/plain; charset=UTF-8 |
| Content-Transfer-Encoding | 8bit |
| X-Trace | adenine.netfront.net 1304411518 17644 118.90.133.108 (3 May 2011 08:31:58 GMT) |
| X-Complaints-To | news@netfront.net |
| NNTP-Posting-Date | Tue, 3 May 2011 08:31:58 +0000 (UTC) |
| X-Face | ?)Aw4rXwN5u0~$nqKj`xPz>xHCwgi^q+^?Ri*+R(&uv2=E1Q0Zk(>h!~o2ID@6{uf8s;a +M[5[U[QT7xFN%^gR"=tuJw%TXXR'Fp~W;(T"1(739R%m0Yyyv*gkGoPA.$b,D.w:z+<'"=-lVT?6 {T?=R^:W5g|E2#EhjKCa+nt":4b}dU7GYB*HBxn&Td$@f%.kl^:7X8rQWd[NTc"P"u6nkisze/Q;8 "9Z{peQF,w)7UjV$c|RO/mQW/NMgWfr5*$-Z%u46"/00mx-,\R'fLPe.)^ |
| User-Agent | slrn/pre1.0.0-18 (Linux) |
| Xref | x330-a1.tempe.blueboxinc.net comp.databases.postgresql:113 |
Show key headers only | View raw
On 2011-05-03, Laurenz Albe <invite@spam.to.invalid> wrote: > Matthew Woodcraft wrote: >> What I don't see a firm guarantee for is that ORDER BY on a SELECT FOR >> UPDATE controls the order in which the locks are taken, as opposed to >> just controlling the order of the result rows. > > > So the locks will be taken in the order specified in ORDER BY in a > simple query, but > a) that is not a documented feature and > b) the commit message suggests that that is not written in stone. IIRC Tom's comment at the time was that, this behaviour would continue until something better was developed. -- ⚂⚃ 100% natural --- Posted via news://freenews.netfront.net/ - Complaints to news@netfront.net ---
Back to comp.databases.postgresql | Previous | Next — Previous in thread | Find similar
Re: Deadlock on the same select for update "Laurenz Albe" <invite@spam.to.invalid> - 2011-05-03 09:53 +0200 Re: Deadlock on the same select for update Jasen Betts <jasen@xnet.co.nz> - 2011-05-03 08:31 +0000
csiph-web