On Tue, Mar 18, 2025 at 1:50 AM Michael Paquier <mich...@paquier.xyz> wrote: > - count > -------- > - 4 > -(1 row) > > This removal done in the regression tests was not intentional.
Yes, thanks for fixing that. > How about adding a check on PIPELINE_COMMAND_COUNT when sending a > query through this path? Should we check for more scenarios with > syncs and flushes as well when sending these queries? I've added additional tests when piping queries with ';': - I've reused the same scenario with \sendpipeline: single query, multiple queries, flushes, syncs, using COPY... - Using ';' will replace the unnamed prepared statement. It's a bit different from expected as a simple query will delete the unnamed prepared statement. - Sending an extended query prepared with \bind using a ';' on a newline, though this is not specific to pipelining. The scanned semicolon triggers the call to SendQuery, processing the buffered extended query. It's a bit unusual but that's the current behaviour.
v03-0001-psql-Allow-to-add-queries-in-an-ongoing-pipeline.patch
Description: Binary data
