Skip site navigation (1) Skip section navigation (2)

Re: 6.5.0 datetime bug?

From: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: gravity(at)dds(dot)nl
Cc: "Ross J(dot) Reedstrom" <reedstrm(at)wallace(dot)ece(dot)rice(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: 6.5.0 datetime bug?
Date: 2000-03-31 14:59:21
Message-ID: 38E4BD49.6ACF8660@alumni.caltech.edu (view raw or flat)
Thread:
Lists: pgsql-hackers
> > Hmm, I happen to have a 6.5.0 system sitting here: It works there, so I suspect
> > something with your local operating system config.
> now, this is weird.

I should have asked originally: what time zone are you running in?
>From your mailing address I'll bet that you are on the other side of
GMT from where I run my tests:

postgres=# set time zone 'Europe/Amsterdam';
SET VARIABLE
postgres=# select date_part('day',
'3-27-2000'::timestamp-'3-6-2000'::timestamp) as days;
 days 
------
   20
(1 row)

OK, I see the problem in current sources :(

Thanks for pursuing this; I'll take a look at it.

btw, if we were to add some "other side of GMT" time zone testing to
our regression test, what time zone would be the most likely to be
universally supported? We know that PST8PDT works pretty well, but I'm
not sure of the best candidate for the other side...

                    - Thomas

-- 
Thomas Lockhart				lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California

In response to

pgsql-hackers by date

Next:From: Karel ZakDate: 2000-03-31 15:33:29
Subject: procedure returns a tuple
Previous:From: Thomas LockhartDate: 2000-03-31 14:50:37
Subject: Re: Docs refreshed

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group