Re: Wrong usage of pqMsg_Close message code?
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Tatsuo Ishii <ishii@sraoss.co.jp>, pavel.stehule@gmail.com,
aleksander@timescale.com, pgsql-hackers@lists.postgresql.org
Date: 2023-08-29T14:01:47Z
Lists: pgsql-hackers
Michael Paquier <michael@paquier.xyz> 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
Commits
-
Fix misuse of PqMsg_Close.
- 6475e663b3c6 17.0 landed