| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | 蔡梦娟(玊于) <mengjuan(dot)cmj(at)alibaba-inc(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, alvherre <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | 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-09-22 03:52:34 |
| Message-ID: | 0a291fee-dd99-abbc-434d-e37eace696cd@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021/09/22 1:14, 蔡梦娟(玊于) wrote:
> Hi all, I want to know your opinion on this patch, or in what way do you think we should solve this problem?
I agree that something like the patch (i.e., introduction of promotion
from cancel request to terminate one) is necessary for the fix. One concern
on the patch is that the cancel request can be promoted to the terminate one
even when secure_write() doesn't actually get stuck. Is this acceptable?
Maybe I'm tempted to set up the duration until the promotion happens....
Or we should introduce the dedicated timer for communication on the socket?
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-09-22 03:53:26 | Re: Estimating HugePages Requirements? |
| Previous Message | Amit Kapila | 2021-09-22 03:50:07 | Re: row filtering for logical replication |