From: Tom Lane <tgl@sss.pgh.pa.us>
To: Campbell, Lance <lance@illinois.edu>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: pg_dump error
Date: Mon, 20 Jul 2015 09:59:50 -0400
Message-ID: <14015.1437400790@sss.pgh.pa.us> (raw)
In-Reply-To: <B75CD08C73BD3543B97E4EF3964B7D701FF53A92@CITESMBX1.ad.uillinois.edu>
References: <B75CD08C73BD3543B97E4EF3964B7D701FF539B8@CITESMBX1.ad.uillinois.edu>
<B75CD08C73BD3543B97E4EF3964B7D701FF53A92@CITESMBX1.ad.uillinois.edu>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
"Campbell, Lance" <lance@illinois.edu> writes:
> As a follow-up I ran this command:
> pg_dump -U username -h localhost databasename -f databasename.20150720
> I get this in the console:
> pg_dump: [archiver (db)] query failed: SSL error: unexpected message
> pg_dump: [archiver (db)] query was: SET search_path = calendar, pg_catalog
That looks like you've run into the renegotiation bug that Red Hat
introduced in their last openssl patch:
https://bugzilla.redhat.com/show_bug.cgi?id=1234487
So basically things will work until you exceed a couple gigabytes of
traffic on the connection, and then bang.
The workaround we're recommending to people is to set
ssl_renegotiation_limit to zero (disable it) in postgresql.conf, as
renegotiation seems to create way more problems than it fixes (this
RH bug was very far from the first such problem, and it's not likely
to be the last either).
See recent discussions on pgsql-hackers, where it was more or less
agreed that we're going to remove the feature altogether in the future.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, lance@illinois.edu
Subject: Re: pg_dump error
In-Reply-To: <14015.1437400790@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox