On Thu, Jun 23, 2016 at 07:47:10AM +0300, Dmitry Igrishin wrote:
> 2016-06-23 1:53 GMT+03:00 Bruce Momjian <br...@momjian.us>:
> > On Thu, Jun 9, 2016 at 03:38:40PM +0300, Dmitry Igrishin wrote:
> >> Hi,
> >>
> >> At https://www.postgresql.org/docs/9.6/static/protocol-flow.html
> >> The StartupMessage instead of "startup message" may looks better for
> >> the reader (at least for me).
> >
> > Uh, where exactly? Here?
> I suggest everywhere on this page.
> >
> > To begin a session, a frontend opens a connection to the server and
> > sends a startup message.
> >
> > In that case, it is highlighting it is a startup message, not the exact
> > message identifier.
> Yes, but see the next sentence: "This message includes the names of
> the user and of the database the user wants to connect to; it also
> identifies the particular protocol version to be used." So, it's about
> the StartupMessage exactly.
OK, how is this attached doc patch?
--
Bruce Momjian <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml
new file mode 100644
index 9c96d8f..04d6780
*** a/doc/src/sgml/protocol.sgml
--- b/doc/src/sgml/protocol.sgml
***************
*** 93,99 ****
length of the rest of the message (this length count includes itself, but
not the message-type byte). The remaining contents of the message are
determined by the message type. For historical reasons, the very first
! message sent by the client (the startup message) has no initial
message-type byte.
</para>
--- 93,99 ----
length of the rest of the message (this length count includes itself, but
not the message-type byte). The remaining contents of the message are
determined by the message type. For historical reasons, the very first
! message sent by the client (StartupMessage) has no initial
message-type byte.
</para>
***************
*** 213,221 ****
<para>
To begin a session, a frontend opens a connection to the server and sends
! a startup message. This message includes the names of the user and of the
database the user wants to connect to; it also identifies the particular
! protocol version to be used. (Optionally, the startup message can include
additional settings for run-time parameters.)
The server then uses this information and
the contents of its configuration files (such as
--- 213,222 ----
<para>
To begin a session, a frontend opens a connection to the server and sends
! a startup message (StartupMessage). This message includes the names
! of the user and of the
database the user wants to connect to; it also identifies the particular
! protocol version to be used. (Optionally, StartupMessage can include
additional settings for run-time parameters.)
The server then uses this information and
the contents of its configuration files (such as
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
