| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Question about non-blocking mode in libpq |
| Date: | 2023-10-31 16:58:18 |
| Message-ID: | ZUEyKtrtl3IoTwWW@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 21, 2021 at 10:15:09AM +0900, Yugo NAGATA wrote:
> I understood that, although PQgetResult() also flushes the buffer, we still
> should call PQflush() beforehand because we would not like get blocked after
> calling PQgetResult(). Thanks.
I modified your patch, attached, that I would like to apply to all
supported versions.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
| Attachment | Content-Type | Size |
|---|---|---|
| block.diff | text/x-diff | 741 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Morris | 2023-10-31 17:11:26 | Re: Add the ability to limit the amount of memory that can be allocated to backends. |
| Previous Message | Nathan Bossart | 2023-10-31 16:58:02 | Re: Fix search_path for all maintenance commands |