From: | Steve Atkins <steve(at)blighty(dot)com> |
---|---|
To: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: SSL connection lost after long-lasting copy command |
Date: | 2010-02-09 20:56:00 |
Message-ID: | 6034EF04-97EC-4153-AEAE-9D33ADB1DC73@blighty.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Feb 9, 2010, at 9:55 AM, Seb wrote:
> On Tue, 9 Feb 2010 14:44:23 -0300,
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
>
> [...]
>
>> Err, remove the renegotiation code from the server.
>
> Oh I meant something from a user's point of view, not hacking the source
> code. If there's not a user option, I don't mind the connection loss as
> long as the data do get copied to the table. Thanks.
Your only real option that doesn't require recompilation right now
is to avoid using SSL.
Your operating system provider is shipping openssl libraries that are
(intentionally) broken. If you want to use the versions of openssl and
postgresql they provide they won't work with long running SSL
connections until they've fixed one or the other.
Cheers,
Steve
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2010-02-09 21:12:03 | Re: vacuumdb ERROR: out of memory |
Previous Message | John R Pierce | 2010-02-09 20:55:39 | Re: vacuumdb ERROR: out of memory |