Re: CHECK_FOR_INTERRUPTS in spgdoinsert() isn't helpful
От | Peter Geoghegan |
---|---|
Тема | Re: CHECK_FOR_INTERRUPTS in spgdoinsert() isn't helpful |
Дата | |
Msg-id | CAM3SWZQYkP997-J0Yq0-FhvWnbyQfXkPtdyhe6zYq=PO_W_+BQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: CHECK_FOR_INTERRUPTS in spgdoinsert() isn't helpful (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: CHECK_FOR_INTERRUPTS in spgdoinsert() isn't helpful
|
Список | pgsql-hackers |
On Thu, May 29, 2014 at 1:42 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Not throw the error. (If we did, it'd turn into a PANIC, which doesn't > seem like what we want.) Of course, but it isn't obvious to me that that isn't what we'd want, if the alternative is definitely that we'd be stuck in an infinite uninterruptible loop (I guess we couldn't just avoid throwing the error, thereby risking proceeding without locks -- and so I guess we can basically do nothing like this in critical sections). Now, that probably isn't the actual choice that we must face, but it also isn't obvious to me how you can do better than not throwing the error (and doing nothing extra) when in a critical section. That was the intent of my original question. -- Peter Geoghegan
В списке pgsql-hackers по дате отправления: