Re: Hot Standy introduced problem with query cancel behavior
От | Tom Lane |
---|---|
Тема | Re: Hot Standy introduced problem with query cancel behavior |
Дата | |
Msg-id | 24182.1262103183@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Hot Standy introduced problem with query cancel behavior (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: Hot Standy introduced problem with query cancel
behavior
|
Список | pgsql-hackers |
Andres Freund <andres@anarazel.de> writes: > On Tuesday 29 December 2009 16:22:54 Tom Lane wrote: >> This seems like a fairly bad idea. One of the intended use-cases is to >> be able to manually "kill -INT" a misbehaving backend. Assuming that >> there will be valid info about the signal in shared memory will break >> that. > Well. That already is the case now. MyProc->recoveryConflictMode is checked to > recognize what kind of conflict is being resolved... In that case, HS has already broken it, and we need to fix it not make it worse. My humble opinion is that SIGINT should not be overloaded with multiple meanings. We already have a multiplexed signal mechanism, which is what should be used for any additional signal reasons HS may need to introduce. regards, tom lane
В списке pgsql-hackers по дате отправления: