1berry/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix documentation problem pointed out by Barry Lind: code expected a

Browse Source 
terminating zero byte in StartupMessage, docs didn't mention it.
This commit is contained in:
Tom Lane 2003-05-08 14:35:24 +00:00
parent 1718f4c66c
commit 4e08d35e7d
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/src/sgml/protocol.sgml
View File

@ -1,4 +1,4 @@
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/protocol.sgml,v 1.37 2003/05/07 21:46:15 tgl Exp $ --> <!-- $Header: /cvsroot/pgsql/doc/src/sgml/protocol.sgml,v 1.38 2003/05/08 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)
</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)
</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)
</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>