Re: Transactions involving multiple postgres foreign servers, take 2
От | Ashutosh Bapat |
---|---|
Тема | Re: Transactions involving multiple postgres foreign servers, take 2 |
Дата | |
Msg-id | CAExHW5u91OT7Jq2CDbpDPU-sbMPD0scdcm3Zd02Ww6xD_P393A@mail.gmail.com обсуждение исходный текст |
Ответ на | RE: Transactions involving multiple postgres foreign servers, take 2 ("tsunakawa.takay@fujitsu.com" <tsunakawa.takay@fujitsu.com>) |
Ответы |
Re: Transactions involving multiple postgres foreign servers, take 2
RE: Transactions involving multiple postgres foreign servers, take 2 |
Список | pgsql-hackers |
On Mon, Oct 19, 2020 at 2:37 PM tsunakawa.takay@fujitsu.com <tsunakawa.takay@fujitsu.com> wrote: > > Really. I thought we were talking about canceling commits with Ctrl + C as you referred, right? I couldn't imagine, inproduction environments where many sessions are running transactions concurrently, how the user (DBA) wants and can canceleach stuck session during commit one by one with Ctrl + C by hand. I haven't seen such a feature exist or been consideredcrucial that enables the user (administrator) to cancel running processing with Ctrl + C from the side. Using pg_cancel_backend() and pg_terminate_backend() a DBA can cancel running query from any backend or terminate a backend. For either to work the backend needs to be interruptible. IIRC, Robert had made an effort to make postgres_fdw interruptible few years back. -- Best Wishes, Ashutosh Bapat
В списке pgsql-hackers по дате отправления: