RE: Transactions involving multiple postgres foreign servers, take 2
От | tsunakawa.takay@fujitsu.com |
---|---|
Тема | RE: Transactions involving multiple postgres foreign servers, take 2 |
Дата | |
Msg-id | TYAPR01MB299000CF6510647AF5B6F4B1FE1F0@TYAPR01MB2990.jpnprd01.prod.outlook.com обсуждение исходный текст |
Ответ на | Re: Transactions involving multiple postgres foreign servers, take 2 (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>) |
Ответы |
Re: Transactions involving multiple postgres foreign servers, take 2
|
Список | pgsql-hackers |
From: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com> > 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. Yeah, I know those functions. Sawada-san was talking about Ctrl + C, so I responded accordingly. Also, how can the DBA find sessions to run those functions against? Can he tell if a session is connected to or runningSQL to a given foreign server? Can he terminate or cancel all session with one SQL command that are stuck in accessinga particular foreign server? Furthermore, FDW is not cancellable in general. So, I don't see a point in trying hard to make only commit be cancelable. Regards Takayuki Tsunakawa
В списке pgsql-hackers по дате отправления: