Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6])
	by hub.org (8.9.3/8.9.1) with ESMTP id SAA51669;
	Wed, 28 Apr 1999 18:29:56 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id SAA12392;
	Wed, 28 Apr 1999 18:29:18 -0400 (EDT)
To: Michael J Davis <michael.j.davis@tvguide.com>
cc: pgsql-interfaces@postgreSQL.org, pgsql-hackers@postgreSQL.org
Subject: Re: [HACKERS] Issues with the latest 6.5 source 
In-reply-to: Your message of Tue, 27 Apr 1999 16:31:08 -0500
	<93C04F1F5173D211A27900105AA8FCFC145430@lambic.prevuenet.com>
Date: Wed, 28 Apr 1999 18:29:18 -0400
Message-ID: <12390.925338558@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Michael J Davis <michael.j.davis@tvguide.com> writes:
> 1)	The \g option in pgsql is failing.

Fixed.  I had managed to break the empty-query response protocol on
Sunday --- odd that none of the regression tests detected this.  Sigh.

> 2)	My Access97 application using ODBC can't connect to the database.

I now have a strong suspicion that this is caused by the same goof.
ODBC might issue an empty query during startup.  (That used to be a
necessary part of the startup protocol; it isn't anymore, but ODBC
very possibly hasn't been changed.)

If you don't have CVS access and don't want to wait for tonight's
snapshot, here is the patch:

*** src/backend/tcop/dest.c~	Wed Apr 28 18:15:07 1999
--- src/backend/tcop/dest.c	Wed Apr 28 18:15:45 1999
***************
*** 336,342 ****
  			 *		tell the fe that we saw an empty query string
  			 * ----------------
  			 */
! 			pq_putbytes("I", 1);
  			break;
  
  		case Local:
--- 336,342 ----
  			 *		tell the fe that we saw an empty query string
  			 * ----------------
  			 */
! 			pq_putbytes("I", 2); /* note we send I and \0 */
  			break;
  
  		case Local:


Let us know if that helps...

			regards, tom lane