FYI: snapshot 4/28/1999 (fwd)

Started by Peter T Mountalmost 27 years ago5 messageshackers
Jump to latest
#1Peter T Mount
peter@retep.org.uk

I just received this. Any ideas ?

--
Peter T Mount peter@retep.org.uk
Main Homepage: http://www.retep.org.uk
PostgreSQL JDBC Faq: http://www.retep.org.uk/postgres
Java PDF Generator: http://www.retep.org.uk/pdf

---------- Forwarded message ----------
Date: Wed, 28 Apr 1999 16:36:56 -0500
From: Brian P Millett <bpm@ec-group.com>
To: Peter T Mount <peter@retep.org.uk>
Subject: FYI: snapshot 4/28/1999

Peter, thought that you would like to know that the snapshot for today
will not allow a jdbc connection. I don't know if this is a jdk
security 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 Millett
Enterprise Consulting Group "Heaven can not exist,
(314) 205-9030 If the family is not eternal"
bpm@ec-group.com F. Ballard Washburn

#2Michael J Davis
michael.j.davis@tvguide.com
In reply to: Peter T Mount (#1)
RE: [HACKERS] FYI: snapshot 4/28/1999 (fwd)

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 PM
To: PostgreSQL Hackers List
Subject: [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.uk
PostgreSQL JDBC Faq: http://www.retep.org.uk/postgres
Java PDF Generator: http://www.retep.org.uk/pdf

---------- Forwarded message ----------
Date: Wed, 28 Apr 1999 16:36:56 -0500
From: Brian P Millett <bpm@ec-group.com>
To: Peter T Mount <peter@retep.org.uk>
Subject: FYI: snapshot 4/28/1999

Peter, thought that you would like to know that the snapshot for
today
will not allow a jdbc connection. I don't know if this is a jdk
security 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 Millett
Enterprise Consulting Group "Heaven can not exist,
(314) 205-9030 If the family is not eternal"
bpm@ec-group.com F. Ballard Washburn

#3Peter T Mount
peter@retep.org.uk
In reply to: Michael J Davis (#2)
RE: [HACKERS] FYI: snapshot 4/28/1999 (fwd)

The weird thing is that the JDBC driver hasn't been sending an empty
string since 6.2.x. Starting from 6.3, I replaced the empty string with
a query to fetch the current DATESTYLE so the date and time code would
work properly.

It would be interesting to see if this patch fixes it however.

Peter (@work)

--
Peter T Mount, IT Section
petermount@it.maidstone.gov.uk
Anything I write here are my own views, and cannot be taken as the
official words of Maidstone Borough Council

-----Original Message-----
From: Michael J Davis [mailto:michael.j.davis@tvguide.com]
Sent: Thursday, April 29, 1999 7:04 AM
To: 'Peter T Mount'; PostgreSQL Hackers List
Subject: RE: [HACKERS] FYI: snapshot 4/28/1999 (fwd)

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 PM
To: PostgreSQL Hackers List
Subject: [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.uk
PostgreSQL JDBC Faq: http://www.retep.org.uk/postgres
Java PDF Generator: http://www.retep.org.uk/pdf

---------- Forwarded message ----------
Date: Wed, 28 Apr 1999 16:36:56 -0500
From: Brian P Millett <bpm@ec-group.com>
To: Peter T Mount <peter@retep.org.uk>
Subject: FYI: snapshot 4/28/1999

Peter, thought that you would like to know that the snapshot for
today
will not allow a jdbc connection. I don't know if this is a jdk
security 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 Millett
Enterprise Consulting Group "Heaven can not exist,
(314) 205-9030 If the family is not eternal"
bpm@ec-group.com F. Ballard Washburn

#4Tom Lane
tgl@sss.pgh.pa.us
In reply to: Peter T Mount (#3)
Re: [HACKERS] FYI: snapshot 4/28/1999 (fwd)

Peter Mount <petermount@it.maidstone.gov.uk> writes:

The weird thing is that the JDBC driver hasn't been sending an empty
string since 6.2.x.
It would be interesting to see if this patch fixes it however.

I'm unsure whether to blame my empty-query goof for the JDBC problem or
not. You say Monday's snapshot was OK --- but I committed that booboo
on Sunday, so it should have been in Monday's snap. Let us know whether
the problem is still there...

regards, tom lane

#5Brian P Millett
bpm@ec-group.com
In reply to: Tom Lane (#4)
Re: [HACKERS] FYI: snapshot 4/28/1999 (fwd)

Tom Lane wrote:

Peter Mount <petermount@it.maidstone.gov.uk> writes:

The weird thing is that the JDBC driver hasn't been sending an empty
string since 6.2.x.
It would be interesting to see if this patch fixes it however.

I'm unsure whether to blame my empty-query goof for the JDBC problem or
not. You say Monday's snapshot was OK --- but I committed that booboo
on Sunday, so it should have been in Monday's snap. Let us know whether
the problem is still there...

Well Tom,
The patch fixed it. With the snapshot from 4/28/1999, I can now
connect.

Thanks Peter, Michael & Tom.

--
Brian Millett
Enterprise Consulting Group "Heaven can not exist,
(314) 205-9030 If the family is not eternal"
bpm@ec-group.com F. Ballard Washburn