Received: from golem.fourpalms.org (fourpalms.org [64.3.68.148])
	by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0DGS7p61622;
	Sat, 13 Jan 2001 11:28:07 -0500 (EST)
	(envelope-from lockhart@alumni.caltech.edu)
Received: from alumni.caltech.edu (localhost.localdomain [127.0.0.1])
	by golem.fourpalms.org (Postfix) with ESMTP
	id F1B8BFEB0; Sat, 13 Jan 2001 16:30:16 +0000 (UTC)
Message-ID: <3A608298.6ACA84BD@alumni.caltech.edu>
Date: Sat, 13 Jan 2001 16:30:16 +0000
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
Reply-To: lockhart@fourpalms.org
Organization: Yes
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.17-21mdksmp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Barry Lind <barry@xythos.com>, pgsql-patches@postgresql.org,
	pgsql-interfaces@postgresql.org, mcannon@internet.com
Subject: Re: [PATCHES] Patch for JDBC timestamp problems
References: <200101130516.AAA14835@candle.pha.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200101/120
X-Sequence-Number: 730

> Oh, great, I see this patch fixes Mike Cannon's problem too.  I will
> apply it to the main tree now, and it will appear in 7.1.  If you have
> any more improvements, please send them over.  Thanks.

I'm confused, as usual. How does forcing the client time zone to GMT fix
the problem of mismatching client and server time zones? istm that you
still have a problem if the server is not on GMT.

Does creating a static variable affect the threadsafe capabilities of
the driver? If so, it shouldn't be done, but perhaps this is a feature
of the code already?

                      - Thomas