Received: from golem.fourpalms.org (fourpalms.org [64.3.68.148])
	by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0DHATp64118;
	Sat, 13 Jan 2001 12:10:29 -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 B76E5FEB0; Sat, 13 Jan 2001 17:12:42 +0000 (UTC)
Message-ID: <3A608C8A.B0DDEC51@alumni.caltech.edu>
Date: Sat, 13 Jan 2001 17:12:42 +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: lockhart@fourpalms.org, 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: <200101131646.LAA12663@candle.pha.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200101/122
X-Sequence-Number: 732

> > 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.
> No idea.  When it fixed someone's problem, I was excited.

Well, afaict it might have broken most other people, so is not a big
win.

                      - Thomas