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
77a4c51a
Commit
77a4c51a
authored
14 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
Clarify SELECT FOR UPDATE behavior in docs.
parent
b17129b5
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/ref/select.sgml
+4
-3
4 additions, 3 deletions
doc/src/sgml/ref/select.sgml
with
4 additions
and
3 deletions
doc/src/sgml/ref/select.sgml
+
4
−
3
View file @
77a4c51a
<!--
<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/select.sgml,v 1.13
0
2010/0
4/03 07:23:02 petere
Exp $
$PostgreSQL: pgsql/doc/src/sgml/ref/select.sgml,v 1.13
1
2010/0
6/15 20:04:53 momjian
Exp $
PostgreSQL documentation
PostgreSQL documentation
-->
-->
...
@@ -1200,8 +1200,9 @@ FOR SHARE [ OF <replaceable class="parameter">table_name</replaceable> [, ...] ]
...
@@ -1200,8 +1200,9 @@ FOR SHARE [ OF <replaceable class="parameter">table_name</replaceable> [, ...] ]
case of a join query, the rows locked are those that contribute to
case of a join query, the rows locked are those that contribute to
returned join rows. In addition, rows that satisfied the query
returned join rows. In addition, rows that satisfied the query
conditions as of the query snapshot will be locked, although they
conditions as of the query snapshot will be locked, although they
will not be returned if they have since been updated to not satisfy
will not be returned if they were updated after the snapshot
the query conditions. If a <literal>LIMIT</> is used, locking stops
and no longer satisfy the query conditions. If a
<literal>LIMIT</> is used, locking stops
once enough rows have been returned to satisfy the limit (but note that
once enough rows have been returned to satisfy the limit (but note that
rows skipped over by <literal>OFFSET</> will get locked). Similarly,
rows skipped over by <literal>OFFSET</> will get locked). Similarly,
if <literal>FOR UPDATE</literal> or <literal>FOR SHARE</literal>
if <literal>FOR UPDATE</literal> or <literal>FOR SHARE</literal>
...
...
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