Return-Path: postarch
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA18839; Mon, 11 May 92 11:18:55 -0700
Message-Id: <9205111818.AA18839@postgres.Berkeley.EDU>
From: postarch (Postgres Mailing Archive)
Subject: Re: Security, Ports, and abstime bugs
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
Reply-To: mer@postgres.berkeley.edu
In-Reply-To: Your message of "Wed, 06 May 92 00:27:23 PDT."
             <9205060727.AA13052@postgres.Berkeley.EDU> 
Date: Mon, 11 May 92 11:18:46 PDT

you write:

> > Query sent to backend is "create junk (date=abstime)"
> > CREATE
> > Go 
> > * append junk (date = "Jan  1 21:11:11 1992"::abstime)\g
> > 
> > Query sent to backend is "append junk (date = "Jan  1 21:11:11 1992"::absti
 +me)"
> > APPEND
> > Go 
> > * retrieve (junk.all)\g
> >
> > Query sent to backend is "retrieve (junk.all)"
> > ---------------
> > | date        |
> > ---------------
> > | Jan  1 00:11:11 1992 MDT|
> > ---------------
> 
> So where did the 21 hours go????  And Jan 1 is in MST not MDT.  Does this only
> happen on Suns or is it a more general "feature"?  A less drastic but
> related feature happens any time one crosses the daylight/standard time
> boundry - an hour is added/subtracted but the time is still reputed to
> be in the current daylight/standard format.

The abstime adt has been rewritten using real date parsing code.  These
problems will go away with version 4.


Jeff Meredith
mer@postgres.berkeley.edu