Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 38019475A9E for ; Mon, 2 Sep 2002 11:54:14 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 9FE81475A61 for ; Mon, 2 Sep 2002 11:54:13 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g82Fs9ZM023188; Mon, 2 Sep 2002 11:54:09 -0400 (EDT) To: g.hintermayer@inode.at (Gerhard Hintermayer) Cc: pgsql-interfaces@postgresql.org Subject: Re: libpgtcl: pq_recvbuf: unexpected EOF on client connection In-reply-to: References: Comments: In-reply-to g.hintermayer@inode.at (Gerhard Hintermayer) message dated "02 Sep 2002 01:45:38 -0700" Date: Mon, 02 Sep 2002 11:54:08 -0400 Message-ID: <23187.1030982048@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/3 X-Sequence-Number: 3064 g.hintermayer@inode.at (Gerhard Hintermayer) writes: > I constantly keep getting this message in the log files when > disconnection with pg_disconnect (TCL-interface) Yeah, I see it too --- though everything's fine if you just exit the client program without an explicit pg_disconnect. I think the problem is that pg_disconnect shouldn't be unregistering the notifier_channel; I bet TCL thinks it should close the socket when we do that. Then the later PQfinish call will be unable to send the normal termination message to the backend. Probably the best fix is to move the unregister call into PgDelConnectionId(), after we do PQfinish. regards, tom lane