Re: Transactions involving multiple postgres foreign servers, take 2
От | Kyotaro Horiguchi |
---|---|
Тема | Re: Transactions involving multiple postgres foreign servers, take 2 |
Дата | |
Msg-id | 20201020.161626.1346568200333233440.horikyota.ntt@gmail.com обсуждение исходный текст |
Ответ на | Re: Transactions involving multiple postgres foreign servers, take 2 (Masahiko Sawada <masahiko.sawada@2ndquadrant.com>) |
Ответы |
RE: Transactions involving multiple postgres foreign servers, take 2
|
Список | pgsql-hackers |
At Tue, 20 Oct 2020 15:53:29 +0900, Masahiko Sawada <masahiko.sawada@2ndquadrant.com> wrote in > On Tue, 20 Oct 2020 at 13:23, tsunakawa.takay@fujitsu.com > <tsunakawa.takay@fujitsu.com> wrote: > > > > From: Kyotaro Horiguchi <horikyota.ntt@gmail.com> > > > I don't think the inability to cancel all session at once cannot be a > > > reason not to not to allow operators to cancel a stuck session. > > > > Yeah, I didn't mean to discount the ability to cancel queries. I just want to confirm how the user can use the cancellationin practice. I didn't see how the user can use the cancellation in the FDW framework, so I asked about it. We have to think about the user's context if we regard canceling commits as important. > > > > I think it doesn't matter whether in FDW framework or not. The user > normally doesn't care which backend processes connecting to foreign > servers. They will attempt to cancel the query like always if they > realized that a backend gets stuck. There are surely plenty of users > who use query cancellation. The most serious impact from inability of canceling a query on a certain session is that server-restart is required to end such a session. regards. -- Kyotaro Horiguchi NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: