From: | Alban Hertroys <haramrae(at)gmail(dot)com> |
---|---|
To: | Stuart Ford <stuart(dot)ford(at)glide(dot)uk(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: SSL connection has been closed unexpectedly |
Date: | 2013-08-15 13:43:07 |
Message-ID: | CAF-3MvN-dd-V0u3UoESm7WGa0sCaweqXhBLrD2vrGj0a8vHhMw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 15 August 2013 15:29, Stuart Ford <stuart(dot)ford(at)glide(dot)uk(dot)com> wrote:
> Alban
>
> I would agree with you, except
...that you misread what I wrote ;)
> it still happens even after I have disabled
> all SSL related stuff in postgresql.conf and pg_hba.conf.
Well, of course. Why would that make any difference? Your problem is not
SSL related. It would probably happen with a normal connection as well.
That is, unless some SSL-related process on your server is crashing or
something like that.
> I've also no
> evidence of any out of memory events on the server.
>
That's only one of the candidates for processes that kill your connections.
Something or someone is doing that.
There's probably some evidence about this in log files, if you're on an OS
that logs stuff.
--
Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
--
If you can't see the forest for the trees,
Cut the trees and you'll see there is no forest.
From | Date | Subject | |
---|---|---|---|
Next Message | AI Rumman | 2013-08-15 13:47:19 | last_vacuum field in not updated |
Previous Message | Stuart Ford | 2013-08-15 13:29:36 | Re: SSL connection has been closed unexpectedly |