Received: from candle.pha.pa.us (candle.navpoint.com [162.33.245.46]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0OIluq52211; Wed, 24 Jan 2001 13:47:56 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id NAA10102; Wed, 24 Jan 2001 13:47:49 -0500 (EST) From: Bruce Momjian Message-Id: <200101241847.NAA10102@candle.pha.pa.us> Subject: Re: [INTERFACES] ODBC gives pq_recvbuf: unexpected EOF on client connection In-Reply-To: <12654.980102362@sss.pgh.pa.us> "from Tom Lane at Jan 21, 2001 01:39:22 pm" To: Tom Lane Date: Wed, 24 Jan 2001 13:47:49 -0500 (EST) CC: Cedar Cox , PostgreSQL-development , PostgreSQL odbc list X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200101/1027 X-Sequence-Number: 3771 Can someone research this? I heard JDBC has the same problem. > 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 > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026