| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Magnus Hagander <mha(at)sollentuna(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Backbranch releases and Win32 locking |
| Date: | 2006-10-09 14:58:32 |
| Message-ID: | 452A6398.2070201@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Hmm. Not entirely sure. These are all in the SSL codepath. Are you using
> SSL on the machine? Does the problem go away if you don't? (I was
No, we don;t use SSL.
> The normal way is that pgwin32_waitforsinglesocket is called from
> pgwin32_send(), which will always have made the attempt to send data
> first.
My doubt is: can ResetEvent resets signaled state of associated event object?
Look, in any case pgwin32_waitforsinglesocket() resets event before
WSAEventSelect().
pgwin32_send() calls WSASend and if it fails, call pgwin32_waitforsinglesocket().
>
>> It's a pity, but locking problem occurs only on SMP box and
>> requires several hours to reproduce. So we are in testing now.
>
> Yikes, that's definitely not nice :-)
>
> //Magnus
>
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-10-09 15:08:04 | Re: 8.2beta1 crash possibly in libpq |
| Previous Message | Tom Lane | 2006-10-09 14:48:30 | Re: Interface of the R-tree in order to work with postgresql |