From: | Piotr Gackiewicz <gacek(at)intertele(dot)pl> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux |
Date: | 2015-06-23 20:56:16 |
Message-ID: | slrnmojhvg.18n.gacek@gacek.intertele.pl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I wrote:
>> Piotr Gackiewicz <gacek(at)intertele(dot)pl> writes:
>>> $ psql -h localhost -c "SET ssl_renegotiation_limit='3kB'; SELECT repeat('0123456789', 1800);"
>>> SSL error: unexpected message
>>> connection to server was lost
>
>> BTW, are you using any nondefault SSL settings? Because I can't reproduce
>> the failure you show.
>
> Oh, scratch that: I do reproduce that in PG <= 9.3, just not in 9.4 or
> HEAD. Apparently our renegotiation rewrite in 9.4 affects this.
I have even more surprises:
9.4.4 passes test above (9.2.13 does not).
But 9.4.4 pg_dump over ssl still breaks, this time with slightly different error:
$ pg_dump --column-inserts -h localhost4 db > db.dump
pg_dump: [archiver (db)] query failed: connection not open
pg_dump: [archiver (db)] query was: FETCH 100 FROM _pg_dump_cursor
In this case it breaked after dumping 1.7 GB, but this is completely different
data from my previous 9.2.13 tests.
Could it be really two different bugs, as you suspected?
:-/
Regards,
--
Piotr Gackiewicz
From | Date | Subject | |
---|---|---|---|
Next Message | Ted Toth | 2015-06-23 22:56:41 | native api or odbc? |
Previous Message | Andres Freund | 2015-06-23 18:34:30 | Re: cascading replication and replication slots. |