| From: | 邱宇航 <iamqyh(at)gmail(dot)com> |
|---|---|
| To: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru> |
| Cc: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Andrey Borodin <amborodin86(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Transaction timeout |
| Date: | 2023-11-20 03:33:22 |
| Message-ID: | 60ACCBF9-5BAD-457E-9EE9-CEC95A352EB0@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I test the V4 patch and found the backend does't process SIGINT while it's in secure_read.
And it seems not a good choice to report ERROR during secure_read, which will turns into
FATAL "terminating connection because protocol synchronization was lost".
It might be much easier to terminate the backend rather than cancel the backend just like
idle_in_transaction_session_timeout and idle_session_timeout did. But the name of the GUC
might be transaction_session_timeout.
And what about 2PC transaction? The hanging 2PC transaction also hurts server a lot. It’s
active transaction but not active backend. Can we cancel the 2PC transaction and how we
cancel it.
--
Yuhang Qiu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2023-11-20 04:19:41 | Re: pg_upgrade and logical replication |
| Previous Message | Richard Guo | 2023-11-20 02:42:31 | Re: Wrong rows estimations with joins of CTEs slows queries by more than factor 500 |