From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Michael Molz" <michael(dot)molz(at)iwm-software(dot)de> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: database backup throws errors |
Date: | 2011-04-07 14:38:23 |
Message-ID: | 12672.1302187103@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Michael Molz" <michael(dot)molz(at)iwm-software(dot)de> writes:
> were running PostgreSQL 8.4.7 for an CRM System on a Linux machine. Database contains about 540 tables with summary about 2.5 million records. Since this weeks the backup stops with an error message always at the same table. Its irrelevant what tool we use to backup (pgAdmin III, pg_dump from a windows client; backup on the Linux machine directly, ...), error stays the same.
> The log contains the following lines:
> 2011-04-05 17:57:35 CEST LOG: SSL-error: unsafe legacy renegotiation disabled
That looks like your problem --- the SSL library is breaking the connection.
> Furthermore, I found a hint to the SSL connection problem. It was recommended to add the parameter ssl_renegotiation_limit with value 0 to postgresql.conf to turn off the SSL renegotiation. As I do this, database system will not start again.
And that's the solution (at least till you can get hold of a non-broken
SSL library). What do you mean by "database system will not start"?
An 8.4.7 server should definitely accept that parameter.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Radosław Smogura | 2011-04-07 14:44:28 | Re: Arrays of arrays |
Previous Message | Michael Gould | 2011-04-07 14:31:20 | Re: Protecting stored procedures |