From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "Jeff Amiel" <becauseimjeff(at)yahoo(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: SSL and crash woes. |
Date: | 2007-08-29 19:11:27 |
Message-ID: | dcc563d10708291211g6a5599e7nc1d264582214f0c9@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 8/29/07, Jeff Amiel <becauseimjeff(at)yahoo(dot)com> wrote:
> A couple of years back (2005) we were setting up replication for the first time (using slony) from
> our production database server to a stand-by box sitting next to it and a remote box in a DR
> site. We were running FreeBSD 5.X/6.X on all systems on Dell servers and postgres 7.4.X and then
> 8.0.X
>
> Replication appeared to crash our production database...a lot. After looking at the core
> dumps/stack traces at the time, we determined that we were crashing in the ssl layers....so we
> disabled SSL (via pg_hba.conf and the slony conn settings) and haven't had an issue for the last
> couple of years.
Interesting. Is it possible that either you've got 2 versions of
openssl? Maybe slony is being compiled against one, then using the
other lib, etc.?
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-08-29 19:13:27 | Re: Out of Memory - 8.2.4 |
Previous Message | Vincenzo Romano | 2007-08-29 19:09:40 | Re: How to avoid "Seq Scans"? |