Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0LIdO045902 for ; Sun, 21 Jan 2001 13:39:24 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f0LIdM912657; Sun, 21 Jan 2001 13:39:22 -0500 (EST) To: Cedar Cox cc: pgsql-interfaces@postgresql.org Subject: Re: ODBC gives pq_recvbuf: unexpected EOF on client connection In-reply-to: References: Comments: In-reply-to Cedar Cox message dated "Sun, 21 Jan 2001 12:47:09 +0200" Date: Sun, 21 Jan 2001 13:39:22 -0500 Message-ID: <12654.980102362@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200101/226 X-Sequence-Number: 844 Cedar Cox writes: > I'm using ODBC/MS Access and every time my client shuts down > I get the log message: > pq_recvbuf: unexpected EOF on client connection > Is there something I'm doing wrong here? Not you, the ODBC driver --- it's just unceremoniously closing the socket connection without being polite enough to send the disconnect message (a single 'X', I think) first. Somebody ought to fix that, but it's not a real high priority. There's no bad side-effects other than cluttering the postmaster log. > (yes I did copy the JDBC post.. ;) I haven't looked at the JDBC code, but evidently it's equally impolite. regards, tom lane