Re: [hensa22@yahoo.es: Re: [pgsql-es-ayuda] SLL error 100% cpu] - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [hensa22@yahoo.es: Re: [pgsql-es-ayuda] SLL error 100% cpu]
Date
Msg-id 11120.1197430327@sss.pgh.pa.us
Whole thread Raw
In response to [hensa22@yahoo.es: Re: [pgsql-es-ayuda] SLL error 100% cpu]  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: [hensa22@yahoo.es: Re: [pgsql-es-ayuda] SLL error 100% cpu]  ("Trevor Talbot" <quension@gmail.com>)
List pgsql-hackers
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 sendfailures when SSL is in use.  While pqcomm.c
hadbeen taught not todo that ages ago, the SSL code was helpfully bleating anyway. Resolves some recent reports such as
bug#3266; however theunderlying 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


pgsql-hackers by date:

Previous
From: "Hiroshi Saito"
Date:
Subject: Re: Problem of a server gettext message.
Next
From: Tom Lane
Date:
Subject: Re: Why my C function is called twice?