Re: "pgstat wait timeout" just got a lot more common on Windows
От
Magnus Hagander
Тема
Re: "pgstat wait timeout" just got a lot more common on Windows
Дата
Msg-id
CABUevEwzMw9zpCpreomUJSdWALbwNjFikdTJu4NbTe5EMrhvPA@mail.gmail.com
Ответ на
Список
Дерево обсуждения
"pgstat wait timeout" just got a lot more common on Windows Tom Lane <tgl@sss.pgh.pa.us>
Re: "pgstat wait timeout" just got a lot more common on Windows Tom Lane <tgl@sss.pgh.pa.us>
Re: "pgstat wait timeout" just got a lot more common on Windows Tom Lane <tgl@sss.pgh.pa.us>
Re: "pgstat wait timeout" just got a lot more common on Windows Magnus Hagander <magnus@hagander.net>
Re: "pgstat wait timeout" just got a lot more common on Windows Tom Lane <tgl@sss.pgh.pa.us>
Re: "pgstat wait timeout" just got a lot more common on Windows Magnus Hagander <magnus@hagander.net>
Re: "pgstat wait timeout" just got a lot more common on Windows Magnus Hagander <magnus@hagander.net>
Re: "pgstat wait timeout" just got a lot more common on Windows Tom Lane <tgl@sss.pgh.pa.us>
On Thu, May 10, 2012 at 6:52 PM, Tom Lane wrote: > I wrote: >> Hence I think we oughta swap the order of those two array >> elements. (Same issue in PGSemaphoreLock, btw, and I'm suspicious of >> pgwin32_select.) > > Oh ... while hacking win32 PGSemaphoreLock I saw that it has a *seriously* > nasty bug: it does not reset ImmediateInterruptOK before returning. > How is it that Windows machines aren't falling over constantly? Hmm. the commit you made to fix it says it changes how ImmediateInterruptOK is handled, but there was not a single line of code that actually changed that? Or am I misreading this completely? -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
В списке pgsql-hackers по дате отправления