| From: | Rafael Martinez Guerrero <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no> |
|---|---|
| To: | Torello Querci <tquerci(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Problem creating index |
| Date: | 2013-08-26 17:50:28 |
| Message-ID: | 521B9564.1050804@usit.uio.no |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 08/26/2013 06:37 PM, Torello Querci wrote:
>
>
> In this moment I get this error while executing the restore of the big
> table in a different database on the same machine:
>
> psql:dump_ess_2013_08_26.sql:271177424: SSL error: sslv3 alert
> unexpected message
> psql:dump_ess_2013_08_26.sql:271177424: connection to server was lost
>
Hello
This error has probably nothing to do with your index problem.
How big is the restore file you are restoring? More than 512MB?
We had a similar error in our RHEL6 servers and the problem was that the
server could not SSL renegotiate. Some systems has SSL libraries that
are incapable of SSL renegotiation as a safeguard against (old) bugs in
the protocol.
If you are doing a restore of a database/table bigger than 512MB and
your system can not do SSL renegotiation, you have to change the
parameter ssl_renegotiation_limit to 0 in your postgresql.conf and
restart postgreSQL.
regards,
--
Rafael Martinez Guerrero
Center for Information Technology
University of Oslo, Norway
PGP Public Key: http://folk.uio.no/rafael/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Crawford | 2013-08-26 18:18:11 | Re: filling database |
| Previous Message | Torello Querci | 2013-08-26 17:01:58 | Re: Problem creating index |