diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2023-11-08 16:44:08 +0100 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2023-11-08 16:44:08 +0100 |
| commit | 1a5594b95762a3c1d3a670881ee7f3c5679a1642 (patch) | |
| tree | 721b7d8fc97387362729127617a72595ffeb7164 /src/backend/access | |
| parent | cd694f60dc975e9fe41e8643ca6f0629283d102e (diff) | |
| download | postgresql-1a5594b95762a3c1d3a670881ee7f3c5679a1642.tar.gz postgresql-1a5594b95762a3c1d3a670881ee7f3c5679a1642.zip | |
Call pqPipelineFlush from PQsendFlushRequest
When PQsendFlushRequest() was added by commit 69cf1d5429d4, 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
Diffstat (limited to 'src/backend/access')
0 files changed, 0 insertions, 0 deletions