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
4e08d35e
Commit
4e08d35e
authored
21 years ago
by
Tom Lane
Browse files
Options
Downloads
Patches
Plain Diff
Fix documentation problem pointed out by Barry Lind: code expected a
terminating zero byte in StartupMessage, docs didn't mention it.
parent
1718f4c6
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/src/sgml/protocol.sgml
+6
-4
6 additions, 4 deletions
doc/src/sgml/protocol.sgml
with
6 additions
and
4 deletions
doc/src/sgml/protocol.sgml
+
6
−
4
View file @
4e08d35e
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/protocol.sgml,v 1.3
7
2003/05/0
7 21:46:15
tgl Exp $ -->
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/protocol.sgml,v 1.3
8
2003/05/0
8 14:35:24
tgl Exp $ -->
<chapter id="protocol">
<chapter id="protocol">
<title>Frontend/Backend Protocol</title>
<title>Frontend/Backend Protocol</title>
...
@@ -2556,7 +2556,7 @@ ErrorResponse (B)
...
@@ -2556,7 +2556,7 @@ ErrorResponse (B)
</VarListEntry>
</VarListEntry>
</VariableList>
</VariableList>
The message body consists of one or more identified fields,
The message body consists of one or more identified fields,
followed by a zero
-
byte terminator. Fields may appear in
followed by a zero
byte
as a
terminator. Fields may appear in
any order. For each field there is the following:
any order. For each field there is the following:
<VariableList>
<VariableList>
<VarListEntry>
<VarListEntry>
...
@@ -2934,7 +2934,7 @@ NoticeResponse (B)
...
@@ -2934,7 +2934,7 @@ NoticeResponse (B)
</VarListEntry>
</VarListEntry>
</VariableList>
</VariableList>
The message body consists of one or more identified fields,
The message body consists of one or more identified fields,
followed by a zero
-
byte terminator. Fields may appear in
followed by a zero
byte
as a
terminator. Fields may appear in
any order. For each field there is the following:
any order. For each field there is the following:
<VariableList>
<VariableList>
<VarListEntry>
<VarListEntry>
...
@@ -3640,7 +3640,9 @@ StartupMessage (F)
...
@@ -3640,7 +3640,9 @@ StartupMessage (F)
</VarListEntry>
</VarListEntry>
</VariableList>
</VariableList>
The protocol version number is followed by one or more pairs of
The protocol version number is followed by one or more pairs of
parameter name and value strings. Parameters can appear in any
parameter name and value strings. A zero byte is required as a
terminator after the last name/value pair.
Parameters can appear in any
order. <literal>user</> is required, others are optional.
order. <literal>user</> is required, others are optional.
Each parameter is specified as:
Each parameter is specified as:
<VariableList>
<VariableList>
...
...
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