client conx problems, 7.3.2

From: Randy Cone <cone(at)hpl(dot)umces(dot)edu>
To: pgsql-bugs(at)postgresql(dot)org
Subject: client conx problems, 7.3.2
Date: 2003-02-26 19:33:48
Message-ID: Pine.LNX.4.53.0302261432350.16335@hpl.umces.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Folks,

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
Feb 26 10:57:46 scylla postgres[25273]: [4] LOG: SSL error: unexpected
record
Feb 26 10:57:46 scylla postgres[25273]: [5] LOG: pq_flush: send() failed:
Connection reset by peer
Feb 26 10:57:46 scylla postgres[25273]: [6] FATAL: Socket command type ^V
unknown

Not sure why I'd even see such a thing over an unencrypted host auth,
especially after removing any possible hostssl access and restarting
posgresql.

Also, when autocommit is off, it happens sooner and more often. When it's
on, still happens, but less often.

(Linux, static binaries, i686, from source, RedHat 8.0.)

Thanks,
RC

Randy Cone
Horn Point Laboratory
University of Maryland Center for Environmental Science
phone#: 410-221-8330 fax#:410-221-8490

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2003-02-26 21:16:14 Re: client conx problems, 7.3.2
Previous Message Huaxin WANG 2003-02-26 04:20:06 Re: Multibyte char encoding atttypmod weirdness