Re: Add PQsendSyncMessage() to libpq
Alvaro Herrera <alvherre@alvh.no-ip.org>
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Michael Paquier <michael@paquier.xyz>
Cc: Jelte Fennema-Nio <postgres@jeltef.nl>, Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>,
Anton Kirilov <antonvkirilov@gmail.com>, Robert Haas <robertmhaas@gmail.com>, pgsql-hackers@postgresql.org
Date: 2024-01-15T09:49:56Z
Lists: pgsql-hackers
On 2024-Jan-15, Michael Paquier wrote: Looks good! Just some small notes, > +/* > + * Wrapper for PQpipelineSync and PQsendPipelineSync. > * > * It's legal to start submitting more commands in the pipeline immediately, > * without waiting for the results of the current pipeline. There's no need to the new function pqPipelineSyncInternal is not a wrapper for these other two functions -- the opposite is true actually. We tend to use the term "workhorse" or "internal workhorse" for this kind of thing. In the docs, after this patch we have - PQpipelineSync - PQsendFlushRequest - PQsendPipelineSync Wouldn't it make more sense to add the new function in the middle of the two existing ones instead? Looking again at the largish comment that's now atop pqPipelineSyncInternal(), I think most of it should be removed -- these things should be explained in the SGML docs, and I think they are, in the "Using Pipeline Mode" section. We can just have the lines this patch is adding. -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/ "I can't go to a restaurant and order food because I keep looking at the fonts on the menu. Five minutes later I realize that it's also talking about food" (Donald Knuth)
Commits
-
Remove some comments related to pqPipelineSync() and PQsendPipelineSync()
- 061cc7eacac1 17.0 landed
-
libpq: Add PQsendPipelineSync()
- 4794c2d31714 17.0 landed
-
Fix stop condition for dumping GRANT commands
- 7b7fa8513033 16.0 cited