Alvaro Herrera 42f8326851 Call pqPipelineFlush from PQsendFlushRequest ... When PQsendFlushRequest() was added by commit 69cf1d5429, we argued against adding a PQflush() call in it[1]. This is still the right decision: if the user wants a flush to occur, they can just call that. However, we failed to realize that the message bytes could still be given to the kernel for transmitting when this can be made without blocking. That's what pqPipelineFlush() does, and it is done for every single other message type sent by libpq, so do that. (When the socket is in blocking mode this may indeed block, but that's what all the other libpq message-sending routines do, too.) [1] https://www.postgresql.org/message-id/202106252352.5ca4byasfun5%40alvherre.pgsql Author: Jelte Fennema-Nio <postgres@jeltef.nl> Discussion: https://postgr.es/m/CAGECzQTxZRevRWkKodE-SnJk1Yfm4eKT+8E4Cyq3MJ9YKTnNew@mail.gmail.com		2023-11-08 16:44:08 +01:00
..
ecpg	Translation updates	2023-11-06 13:10:09 +01:00
libpq	Call pqPipelineFlush from PQsendFlushRequest	2023-11-08 16:44:08 +01:00
Makefile	Fix parallel make when running make install before make all	2011-03-08 23:52:29 +02:00
meson.build	Update copyright for 2023	2023-01-02 15:00:37 -05:00