Alvaro Herrera <alvherre@alvh.no-ip.org> writes: > This guy is using 8.2.5. SSL seems to be able to fill his log files at > full speed. Are you *sure* the server is 8.2.5? 8.2.5 shouldn't emit duplicate messages, but 8.2.4 and before would: 2007-05-17 21:20 tgl * src/backend/libpq/: be-secure.c (REL7_4_STABLE), be-secure.c (REL8_1_STABLE), be-secure.c (REL8_0_STABLE), be-secure.c (REL8_2_STABLE), be-secure.c: Remove redundant logging of send failures when SSL is in use. While pqcomm.c had been taught not to do that ages ago, the SSL code was helpfully bleating anyway. Resolves some recent reports such as bug #3266; however the underlying cause of the related bug #2829 is still unclear. Furthermore, it looks to me like "SSL SYSCALL error: %m" doesn't exist anymore since that patch, so my bogometer is buzzing loudly. I dunno anything about how to fix the real problem (what's winsock error 10004?), but I don't think he'd be seeing full speed log filling in 8.2.5. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend

"Trevor Talbot" <quension@gmail.com> writes: > On 12/11/07, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> I dunno anything about how to fix the real problem (what's winsock error >> 10004?), > WSAEINTR, "A blocking operation was interrupted by a call to > WSACancelBlockingCall." Oh, then it's exactly the same thing as our bug #2829. I opined in that thread that OpenSSL was broken because it failed to treat this as a retryable case like EINTR. But not being much of a Windows person, that might be mere hot air. Someone with a Windows build environment should try patching OpenSSL to treat WSAEINTR the same as Unix EINTR and see what happens ... regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq