Re: BUG #14062: pg_dump dies after dumping first 60 gigabytes of text for large table

From: D <dll(at)sonic(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14062: pg_dump dies after dumping first 60 gigabytes of text for large table
Date: 2016-04-06 01:53:31
Message-ID: 57046C1B.50007@sonic.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Amazon RDS instance has a default value of 0 for ssl_renegotiation_limit for
the postgres 9.4 default parameters, according to the RDS Dashboard.

However, when we disable SSL connections the problem evaporates. Good enough
for me.

Thanks, Tom!

On 4/4/2016 12:56 PM, Tom Lane wrote:
> dll(at)sonic(dot)net writes:
>> For an approximately 500 gigabyte database, pg_dump dies after approximately
>> 60 gb of text output, with an error:
>
>> pg_dump: Dumping the contents of table "datum" failed: PQgetCopyData()
>> failed.
>> pg_dump: Error message from server: SSL SYSCALL error: EOF detected
>
> Sounds like an SSL renegotiation bug. We gave up on that mess and
> disabled renegotiation by default as of 9.4.5 or so, but maybe you have
> an explicit nonzero setting for ssl_renegotiation_limit?
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message yuanrui 2016-04-06 06:04:08 Wrong result of <select distinct geometry from XXX>
Previous Message Noah Misch 2016-04-06 00:57:00 Re: Breakage with VACUUM ANALYSE + partitions