database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-10-18 04:29:09 +03:00
Code Activity

Update copyright for 2015

Browse Source 
Backpatch certain files through 9.0
This commit is contained in:
Bruce Momjian
2015-01-06 11:43:47 -05:00
parent adfc157dd9
commit 4baaf863ec
1377 changed files with 1384 additions and 1384 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/test/isolation/specs/nowait-2.spec
View File

@@ -34,4 +34,4 @@ permutation "s1a" "s2a" "s2b" "s1b" "s2c"
permutation "s2a" "s1a" "s2b" "s1b" "s2c"
# s2 acquires SHARE then UPDATE, then s1 tries to acquire SHARE but
# can't so aborts because it can't acquire a regular lock
permutation "s2a" "s2b" "s1a" "s1b" "s2c"
permutation "s2a" "s2b" "s1a" "s1b" "s2c"

2
src/test/isolation/specs/nowait-3.spec
View File

@@ -30,4 +30,4 @@ step "s3a" { SELECT * FROM foo FOR UPDATE NOWAIT; }
step "s3b" { COMMIT; }
# s3 skips to second record due to tuple lock held by s2
permutation "s1a" "s2a" "s3a" "s1b" "s2b" "s3b"
permutation "s1a" "s2a" "s3a" "s1b" "s2b" "s3b"

2
src/test/isolation/specs/skip-locked-4.spec
View File

@@ -33,4 +33,4 @@ step "s2f" { COMMIT; }
# because it has a snapshot that sees the older version, we reach the
# waiting code in EvalPlanQualFetch which skips rows when in SKIP
# LOCKED mode, so s1 sees the second row
permutation "s2a" "s1a" "s2b" "s2c" "s2d" "s2e" "s1b" "s2f"
permutation "s2a" "s1a" "s2b" "s2c" "s2d" "s2e" "s1b" "s2f"