The following patch was posted this evening by Tom Lane that could fix your
problem. It fixed a similar problem I was having with ODBC.
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:
-----Original Message-----From: Peter T Mount [SMTP:peter@retep.org.uk]Sent: Wednesday, April 28, 1999 11:50
PMTo: PostgreSQL Hackers ListSubject: [HACKERS] FYI: snapshot 4/28/1999 (fwd)
I just received this. Any ideas ?
-- Peter T Mount peter@retep.org.uk Main Homepage: http://www.retep.org.ukPostgreSQL JDBC Faq:
http://www.retep.org.uk/postgresJava PDF Generator: http://www.retep.org.uk/pdf
---------- Forwarded message ----------Date: Wed, 28 Apr 1999 16:36:56 -0500From: Brian P Millett <bpm@ec-group.com>To:
PeterT Mount <peter@retep.org.uk>Subject: FYI: snapshot 4/28/1999
Peter, thought that you would like to know that the snapshot for
todaywill not allow a jdbc connection. I don't know if this is a jdksecurity thing, or not. The snapshot from Monday,
allows
connections.
I'm using jdk1.2.1, solaris 2.7, WorkShop Compilers 5.0 98/12/15 C
5.0
--Brian MillettEnterprise Consulting Group "Heaven can not exist,(314) 205-9030 If the family
isnot eternal"bpm@ec-group.com F. Ballard Washburn
