| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
| Cc: | "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Jeff Davis" <pgsql(at)j-davis(dot)com>, "Lee McKeeman" <lmckeeman(at)opushealthcare(dot)com>, "PG Hackers" <pgsql-hackers(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: [BUGS] Status of issue 4593 |
| Date: | 2009-01-13 18:18:40 |
| Message-ID: | 496C86A0.EE98.0025.0@wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
>>> Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> That's not how SELECT FOR UPDATE works. SFU is pessimistic manual
> locking, which is supposed to *wait* for the rows to be exclusively
> available. The deadlock timeout you encountered is the correct
> behaviour, not "serialization failure", which is what happens at
commit
> time when the engine realizes that concurrent transactions are not
> serializably recreateable.
Deadlocks like this are the only kind of serialization error possible
under "traditional" (non-MVCC) databases. These are much more rare in
MVCC than update conflicts, but that doesn't mean they aren't
serialization failures there, too. I think it is a violation of the
standard for PostgreSQL not to report them with SQLSTATE '40001'.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-01-13 18:22:04 | Re: BUG #4613: intarray_del_elem returns an invalid empty array (for nullif comparison) |
| Previous Message | Josh Berkus | 2009-01-13 18:06:44 | Re: [BUGS] Status of issue 4593 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2009-01-13 18:34:49 | Re: [BUGS] Status of issue 4593 |
| Previous Message | Josh Berkus | 2009-01-13 18:06:44 | Re: [BUGS] Status of issue 4593 |