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
efa58e10
Commit
efa58e10
authored
21 years ago
by
Tom Lane
Browse files
Options
Downloads
Patches
Plain Diff
Minor editorializing.
parent
755d1917
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/protocol.sgml
+12
-9
12 additions, 9 deletions
doc/src/sgml/protocol.sgml
with
12 additions
and
9 deletions
doc/src/sgml/protocol.sgml
+
12
−
9
View file @
efa58e10
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/protocol.sgml,v 1.3
5
2003/05/06 2
1:51:41
tgl Exp $ -->
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/protocol.sgml,v 1.3
6
2003/05/06 2
3:10:04
tgl Exp $ -->
<chapter id="protocol">
<title>Frontend/Backend Protocol</title>
...
...
@@ -160,10 +160,11 @@
(but note that these exist only within a session, and are never shared
across sessions). Existing prepared statements and portals are
referenced by names assigned when they were created. In addition,
an <quote>unnamed</> prepared statement and portal exist, for use with
queries that are to be executed and forgotten. This is slightly
more efficient than using named objects, since the backend knows that
it need not save the object's state for re-use.
an <quote>unnamed</> prepared statement and portal exist. Although these
behave largely the same as named objects, operations on them are optimized
for the case of executing a query only once and then discarding it,
whereas operations on named objects are optimized on the expectation
of multiple uses.
</para>
</sect2>
</sect1>
...
...
@@ -869,7 +870,8 @@
zero or more CopyData messages (always one per row), followed by CopyDone.
The backend then reverts to the command-processing mode it was
in before the <command>COPY</> started, and sends CommandComplete.
The frontend cannot abort the transfer (short of closing the connection),
The frontend cannot abort the transfer (except by closing the connection
or issuing a Cancel request),
but it can discard unwanted CopyData and CopyDone messages.
</para>
...
...
@@ -2013,9 +2015,10 @@ CommandComplete (B)
<literal>INSERT <replaceable>oid</replaceable>
<replaceable>rows</replaceable></literal>, where
<replaceable>rows</replaceable> is the number of rows
inserted, and <replaceable>oid</replaceable> is the object ID
of the inserted row if <Replaceable>rows</Replaceable> is 1,
otherwise <Replaceable>oid</Replaceable> is 0.
inserted. <replaceable>oid</replaceable> is the object ID
of the inserted row if <Replaceable>rows</Replaceable> is 1
and the target table has OIDs;
otherwise <Replaceable>oid</Replaceable> is 0.
</Para>
<Para>
...
...
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