On Wed, Dec 29, 2010 at 10:58 AM, Kevin Grittner
<kevin.gritt...@wicourts.gov> wrote:
> "Paul J. Davis" <paul.joseph.da...@gmail.com> wrote:
>
>> After running many queries (millions) a connection will report an
>> error that the server has unexpectedly closed the connection.
>
> What message are you getting? (Copy/paste is a good thing.)
>
> What do you see in the server log at the time of failure?
>
> Are you using a connection pool?
>
> -Kevin
>
Doh, that was on my list of things to add but managed to forget.
The error message reported by the client:
DECLARE CURSOR failed: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
And this intriguing error in the server logs from around that time:
2010-12-28 18:40:02 EST LOG: SSL renegotiation failure
2010-12-28 18:40:02 EST LOG: SSL failed to send renegotiation request
2010-12-28 18:40:02 EST LOG: SSL renegotiation failure
2010-12-28 18:40:02 EST LOG: SSL error: unsafe legacy renegotiation disabled
2010-12-28 18:40:02 EST LOG: could not send data to client:
Connection reset by peer
2010-12-28 18:40:02 EST LOG: SSL error: unsafe legacy renegotiation disabled
2010-12-28 18:40:02 EST LOG: could not receive data from client:
Connection reset by peer
2010-12-28 18:40:02 EST LOG: unexpected EOF on client connection
Googling, I see something that suggests turning off SSL renegotiation
which I'll try next.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
