From: | Torello Querci <tquerci(at)gmail(dot)com> |
---|---|
To: | Rafael Martinez Guerrero <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Problem creating index |
Date: | 2013-08-27 05:20:31 |
Message-ID: | CA+igE6Sm9cTUKMuMk60J1Zb05u3J-T=Og4qQNsyvSDS+Tmeeaw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Yes,
the table is bigger than 512MB.
Thank got your tips.
Best Regard, Torello
2013/8/26 Rafael Martinez Guerrero <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no>
> 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 | Torello Querci | 2013-08-27 05:24:18 | Re: Problem creating index |
Previous Message | yinminmin | 2013-08-27 02:45:25 | [GENERAL] Call for translations |