diff options
| author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2011-05-30 20:42:16 +0300 |
|---|---|---|
| committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2011-05-30 20:47:17 +0300 |
| commit | 3103f9a77d005f9d8b8ef492298bbbbf6c4b843f (patch) | |
| tree | 90c6388951c3cd43f284a88a3ea379513e0e3afc /src/test/isolation/expected | |
| parent | 5177dfefc532ea481bf70d1bb8a493f835a9c57c (diff) | |
| download | postgresql-3103f9a77d005f9d8b8ef492298bbbbf6c4b843f.tar.gz | |
The row-version chaining in Serializable Snapshot Isolation was still wrong.
On further analysis, it turns out that it is not needed to duplicate predicate
locks to the new row version at update, the lock on the version that the
transaction saw as visible is enough. However, there was a different bug in
the code that checks for dangerous structures when a new rw-conflict happens.
Fix that bug, and remove all the row-version chaining related code.
Kevin Grittner & Dan Ports, with some comment editorialization by me.
Diffstat (limited to 'src/test/isolation/expected')
| -rw-r--r-- | src/test/isolation/expected/multiple-row-versions.out | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/test/isolation/expected/multiple-row-versions.out b/src/test/isolation/expected/multiple-row-versions.out index cd31029d17..bbd3ecc0f7 100644 --- a/src/test/isolation/expected/multiple-row-versions.out +++ b/src/test/isolation/expected/multiple-row-versions.out @@ -19,6 +19,6 @@ id txt 1 step c4: COMMIT; step c3: COMMIT; -ERROR: could not serialize access due to read/write dependencies among transactions step wz1: UPDATE t SET txt = 'a' WHERE id = 1; +ERROR: could not serialize access due to read/write dependencies among transactions step c1: COMMIT; |