"Campbell, Lance" <lance@xxxxxxxxxxxx> 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@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
