Re: Time limit for a process to hold Content lock in Buffer Cache
От | Atri Sharma |
---|---|
Тема | Re: Time limit for a process to hold Content lock in Buffer Cache |
Дата | |
Msg-id | CAOeZVidjUr62o5bge+O6DS8PYEFagC_wcw1KCXZWKN_FxFo2=w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Time limit for a process to hold Content lock in Buffer Cache (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Time limit for a process to hold Content lock in Buffer Cache
Re: Time limit for a process to hold Content lock in Buffer Cache |
Список | pgsql-hackers |
> > A little bit --- the timeout won't actually kill the query until the > next time control reaches a CHECK_FOR_INTERRUPTS macro that's not inside > a critical section. We've had issues in the past with particular code > paths that failed to include such a check in a long-running loop, and > there might still be some left. But by and large, it won't take very > long for the query to notice the interrupt. Right.I believe this is part of the standard way in which we handle interrupts,right? Making sure that we cancel a query when the backend is in a state to do so,not when the interrupt actually comes in,right? Regards, Atri -- Regards, Atri l'apprenant
В списке pgsql-hackers по дате отправления: