Re: Wrong usage of pqMsg_Close message code?
От | Tom Lane |
---|---|
Тема | Re: Wrong usage of pqMsg_Close message code? |
Дата | |
Msg-id | 1004809.1693317707@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Wrong usage of pqMsg_Close message code? (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: Wrong usage of pqMsg_Close message code?
|
Список | 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
В списке pgsql-hackers по дате отправления: