Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
a31ff707
Commit
a31ff707
authored
Jun 07, 2011
by
Heikki Linnakangas
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Make ascii-art in comments pgindent-safe, and some other formatting changes.
Kevin Grittner
parent
fc1286d3
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
17 additions
and
13 deletions
+17
-13
src/backend/storage/lmgr/predicate.c
src/backend/storage/lmgr/predicate.c
+17
-13
No files found.
src/backend/storage/lmgr/predicate.c
View file @
a31ff707
...
...
@@ -3814,7 +3814,7 @@ FlagRWConflict(SERIALIZABLEXACT *reader, SERIALIZABLEXACT *writer)
SetRWConflict
(
reader
,
writer
);
}
/*
/*
----------------------------------------------------------------------------
* We are about to add a RW-edge to the dependency graph - check that we don't
* introduce a dangerous structure by doing so, and abort one of the
* transactions if so.
...
...
@@ -3830,6 +3830,7 @@ FlagRWConflict(SERIALIZABLEXACT *reader, SERIALIZABLEXACT *writer)
* One more optimization is that if Tin is declared READ ONLY (or commits
* without writing), we can only have a problem if Tout committed before Tin
* acquired its snapshot.
*----------------------------------------------------------------------------
*/
static
void
OnConflict_CheckForSerializationFailure
(
const
SERIALIZABLEXACT
*
reader
,
...
...
@@ -3842,7 +3843,7 @@ OnConflict_CheckForSerializationFailure(const SERIALIZABLEXACT *reader,
failure
=
false
;
/*
/*
------------------------------------------------------------------------
* Check for already-committed writer with rw-conflict out flagged
* (conflict-flag on W means that T2 committed before W):
*
...
...
@@ -3851,12 +3852,13 @@ OnConflict_CheckForSerializationFailure(const SERIALIZABLEXACT *reader,
*
* That is a dangerous structure, so we must abort. (Since the writer
* has already committed, we must be the reader)
*------------------------------------------------------------------------
*/
if
(
SxactIsCommitted
(
writer
)
&&
(
SxactHasConflictOut
(
writer
)
||
SxactHasSummaryConflictOut
(
writer
)))
failure
=
true
;
/*
/*
------------------------------------------------------------------------
* Check whether the writer has become a pivot with an out-conflict
* committed transaction (T2), and T2 committed first:
*
...
...
@@ -3868,6 +3870,7 @@ OnConflict_CheckForSerializationFailure(const SERIALIZABLEXACT *reader,
* - the writer committed before T2
* - the reader is a READ ONLY transaction and the reader was concurrent
* with T2 (= reader acquired its snapshot before T2 committed)
*------------------------------------------------------------------------
*/
if
(
!
failure
)
{
...
...
@@ -3903,7 +3906,7 @@ OnConflict_CheckForSerializationFailure(const SERIALIZABLEXACT *reader,
}
}
/*
/*
------------------------------------------------------------------------
* Check whether the reader has become a pivot with a committed writer:
*
* T0 ------> R ------> W
...
...
@@ -3913,6 +3916,7 @@ OnConflict_CheckForSerializationFailure(const SERIALIZABLEXACT *reader,
* anomaly if:
* - T0 committed before the writer
* - T0 is READ ONLY, and overlaps the writer
*------------------------------------------------------------------------
*/
if
(
!
failure
&&
SxactIsCommitted
(
writer
)
&&
!
SxactIsReadOnly
(
reader
))
{
...
...
@@ -3950,8 +3954,8 @@ OnConflict_CheckForSerializationFailure(const SERIALIZABLEXACT *reader,
{
/*
* We have to kill a transaction to avoid a possible anomaly from
* occurring. If the writer is us, we can just ereport() to cause
*
a
transaction abort. Otherwise we flag the writer for termination,
* occurring. If the writer is us, we can just ereport() to cause
a
* transaction abort. Otherwise we flag the writer for termination,
* causing it to abort when it tries to commit. However, if the writer
* is a prepared transaction, already prepared, we can't abort it
* anymore, so we have to kill the reader instead.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment