public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Michael Paquier <[email protected]>
Cc: Tatsuo Ishii <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Subject: Re: Wrong usage of pqMsg_Close message code?
Date: Tue, 29 Aug 2023 10:01:47 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <ZO2gx/W5bs/[email protected]>
References: <CAFj8pRBKa2ey+Nm_drj_5Fk-3_zBP7uezP2OrQT1pHeBO7m=6A@mail.gmail.com>
	<[email protected]>
	<ZO0lcXlwln/[email protected]>
	<[email protected]>
	<ZO2gx/W5bs/[email protected]>

Michael Paquier <[email protected]> writes:
> Actually, this may be OK as well as it stands.  One can also say that
> the parallel processing is out of this scope, being used only
> internally.  I cannot keep wondering whether we should put more
> efforts in documenting the parallel worker/leader protocol.  That's
> internal to the backend and out of the scope of this thread, still..

Yeah.  I'm not sure whether the leader/worker protocol needs better
documentation, but the parts of it that are not common with the
frontend protocol should NOT be documented in protocol.sgml.
That would just confuse authors of frontend code.

I don't mind having constants for the leader/worker protocol in
protocol.h, as long as they're in a separate section that's clearly
marked as relevant only for server-internal parallelism.

			regards, tom lane

view thread (10+ messages)  latest in thread

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], [email protected], [email protected], [email protected]
  Subject: Re: Wrong usage of pqMsg_Close message code?
  In-Reply-To: <[email protected]>

* 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