public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dmitry Igrishin <[email protected]>
To: Tom Lane <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: pgsql-docs <[email protected]>
Subject: Re: startup message -> StartupMessage
Date: Thu, 23 Jun 2016 17:23:44 +0300
Message-ID: <CAAfz9KPUpbUszTyjBWsoFpu=9Wcm=7TxZGrNzaHbkJfdY3KfSg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAAfz9KOCKAw07dmeeCzQioqwYkib2cGkUgZ9TEZ7+HB-QER6Jg@mail.gmail.com>
	<[email protected]>
	<CAAfz9KOrYt16BGmL9zA8XnbrfRBY3EkfzmHEEAzd-D5BP0HxMg@mail.gmail.com>
	<[email protected]>
	<[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>

2016-06-23 16:38 GMT+03:00 Tom Lane <[email protected]>:
> Bruce Momjian <[email protected]> writes:
>> On Thu, Jun 23, 2016 at 07:47:10AM +0300, Dmitry Igrishin wrote:
>>> 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?
>
> I do not think these are improvements.  This is introductory text,
> not some kind of formal-language specification.
I can agree with this asserting when the text points to some abstract
message, like "The server then sends an appropriate authentication
request message" (because there are several kinds of authentication
messages). But for the concrete messages, there are consistency like
"The frontend must now send a PasswordMessage containing the
password", or "in the normal case the backend will send some
ParameterStatus messages", except the "During this phase the backend
will attempt to apply any additional run-time parameter settings that
were given in the startup message."

-- 
// Dmitry.


-- 
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

view thread (6+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: startup message -> StartupMessage
  In-Reply-To: <CAAfz9KPUpbUszTyjBWsoFpu=9Wcm=7TxZGrNzaHbkJfdY3KfSg@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox