| From: | Anton Kirilov <antonvkirilov(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Add PQsendSyncMessage() to libpq |
| Date: | 2023-05-21 17:17:18 |
| Message-ID: | c4561817-3dc2-b724-9281-4a8d68104690@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello,
On 05/05/2023 16:02, Anton Kirilov wrote:
> On Thu, 4 May 2023, 11:36 Alvaro Herrera, <alvherre(at)alvh(dot)no-ip(dot)org
> <mailto:alvherre(at)alvh(dot)no-ip(dot)org>> wrote:
>
> On 2023-May-04, Anton Kirilov wrote:
> If you want to make sure it's fully flushed, your only option is to have
> the call block.
>
>
> Surely PQflush() returning 0 would signify that the output buffer has
> been fully flushed?
Since I haven't got any further comments, I assume that I am correct, so
here is an updated version of the patch that should address all feedback
that I have received so far and all issues that I have identified.
Thanks,
Anton Kirilov
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-Add-PQpipelinePutSync-to-libpq.patch | text/x-patch | 11.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-05-21 17:20:01 | Re: createuser --memeber and PG 16 |
| Previous Message | Andres Freund | 2023-05-21 17:13:41 | Re: PG 16 draft release notes ready |