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

dll wrote
> 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@

>  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
>> 
> 
> Hi Tom,
> 
> In my case, ssl disable. 
> 
> it's table "tbwww", size around 70GB. My config server it's similar Redhat
> 7.2 and Postgres 9.5.3
> 
> For erro:
> Line 21172: pg_dump: Dumping the contents of table "tbwww" failed:
> PQgetCopyData() failed.
> Line 21173: pg_dump: Error message from server: server closed the
> connection unexpectedly
> Line 21176: pg_dump: The command was: COPY file.tbwww (fileid, filename,
> filenamedownload, file, filedate, coduser) TO stdout;
> 
> -- 
> Sent via pgsql-bugs mailing list (

> pgsql-bugs@

> )
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs





--
Sent from: http://www.postgresql-archive.org/PostgreSQL-bugs-f2117394.html