Randy Cone <[EMAIL PROTECTED]> writes:
> I'm getting this on large inserts when connecting via perl's DBD::Pg using
> on *both* hostssl and host access methods:
> Feb 26 10:57:23 scylla postgres[25273]: [1] LOG: connection received:
> host=127.0.0.1 port=35399
> Feb 26 10:57:23 scylla postgres[25273]: [2] LOG: connection authorized:
> user=xxxx database=xxxx
> Feb 26 10:57:46 scylla postgres[25273]: [3] LOG: SSL renegotiation
> failure
You sure you are on 7.3.2 --- at both ends? This looks like the problem
allegedly fixed by this patch:
2003-01-08 18:18 momjian
* src/: backend/libpq/be-secure.c, interfaces/libpq/fe-secure.c
(REL7_3_STABLE), backend/libpq/be-secure.c,
interfaces/libpq/fe-secure.c: The second was that renegotiation was
just plain broken. I can't believe I didn't notice this before --
once 64k was sent to/from the server the client would crash.
Basicly, in 7.3 the server SSL code set the initial state to "about
to renegotiate" without actually starting the renegotiation. In
addition, the server and client didn't properly handle the
SSL_ERROR_WANT_(READ|WRITE) error. This is fixed in the second
patch.
Nathan Mueller
which is in 7.3.2 but not earlier releases.
I dunno anything about SSL, so if it is still broken I can't help
... but you could try Nathan Mueller ...
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
