Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Issues with the latest 6.5 source

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael J Davis <michael(dot)j(dot)davis(at)tvguide(dot)com>
Cc: pgsql-interfaces(at)postgreSQL(dot)org, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Issues with the latest 6.5 source
Date: 1999-04-28 22:29:18
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-interfaces
Michael J Davis <michael(dot)j(dot)davis(at)tvguide(dot)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);
  		case Local:
--- 336,342 ----
  			 *		tell the fe that we saw an empty query string
  			 * ----------------
! 			pq_putbytes("I", 2); /* note we send I and \0 */
  		case Local:

Let us know if that helps...

			regards, tom lane

pgsql-hackers by date

Next:From: Michael J DavisDate: 1999-04-29 01:26:13
Subject: RE: [HACKERS] Issues with the latest 6.5 source
Previous:From: Bruce MomjianDate: 1999-04-28 21:55:54
Subject: Re: [HACKERS] How do I get the backend server into gdb?

pgsql-interfaces by date

Next:From: Massy GhausiDate: 1999-04-28 22:46:53
Subject: RPM for PgAccess 0.96
Previous:From: Ilhuicatzi Cortes J. HenryDate: 1999-04-28 21:51:02
Subject: Pg and Perl!!

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group