Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
6c21105f
Commit
6c21105f
authored
13 years ago
by
Robert Haas
Browse files
Options
Downloads
Patches
Plain Diff
Change "and and" to "and".
Report by Vik Reykja, patch by Kevin Grittner.
parent
9846dcfb
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/src/sgml/mvcc.sgml
+1
-1
1 addition, 1 deletion
doc/src/sgml/mvcc.sgml
with
1 addition
and
1 deletion
doc/src/sgml/mvcc.sgml
+
1
−
1
View file @
6c21105f
...
@@ -547,7 +547,7 @@ SELECT SUM(value) FROM mytab WHERE class = 2;
...
@@ -547,7 +547,7 @@ SELECT SUM(value) FROM mytab WHERE class = 2;
If either transaction were running at the Repeatable Read isolation level,
If either transaction were running at the Repeatable Read isolation level,
both would be allowed to commit; but since there is no serial order of execution
both would be allowed to commit; but since there is no serial order of execution
consistent with the result, using Serializable transactions will allow one
consistent with the result, using Serializable transactions will allow one
transaction to commit and
and
will roll the other back with this message:
transaction to commit and will roll the other back with this message:
<screen>
<screen>
ERROR: could not serialize access due to read/write dependencies among transactions
ERROR: could not serialize access due to read/write dependencies among transactions
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment