| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, 蔡梦娟(玊于) <mengjuan(dot)cmj(at)alibaba-inc(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Queries that should be canceled will get stuck on secure_write function |
| Date: | 2021-08-27 20:07:02 |
| Message-ID: | CA+TgmoZD30=mmmxyYqA-XNJzd51bCESDAz38iCg3MEsGnx1vGw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Aug 27, 2021 at 3:24 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> I wonder if we could improve the situation somewhat by using the non-blocking
> pqcomm functions in a few select places. E.g. if elog.c's
> send_message_to_frontend() sent its message via a new pq_endmessage_noblock()
> (which'd use the existing pq_putmessage_noblock()) and used
> pq_flush_if_writable() instead of pq_flush(), we'd a) not block sending to the
> client before AbortCurrentTransaction(), b) able to queue further error
> messages safely.
pq_flush_if_writable() could succeed in sending only part of the data,
so I don't see how this works.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2021-08-27 20:10:14 | Re: Queries that should be canceled will get stuck on secure_write function |
| Previous Message | Stephen Frost | 2021-08-27 19:55:46 | Re: log_autovacuum in Postgres 14 -- ordering issue |