Re: PostgreSQL 7.0.2 Date Miscalculation - Mailing list pgsql-bugs

From Darcy Buskermolen
Subject Re: PostgreSQL 7.0.2 Date Miscalculation
Date
Msg-id 3.0.32.20010403074410.03b16048@mail.ok-connect.com
Whole thread Raw
In response to PostgreSQL 7.0.2 Date Miscalculation  (pgsql-bugs@postgresql.org)
List pgsql-bugs
Here is a bit more information on this date type problem.


Welcome to the POSTGRESQL interactive sql monitor:
  Please read the file COPYRIGHT for copyright terms of POSTGRESQL
[PostgreSQL 7.0.2 on i386-unknown-freebsdelf3.4, compiled by gcc 2.7.2.3]

   type \? for help on slash commands
   type \q to quit
   type \g or terminate with semicolon to execute query
 You are currently connected to the database: darcy

darcy=> select date_part('dow','april 1, 2001'::date);
date_part
---------
        6
(1 row)

darcy=> select date_part('dow','april 2, 2001'::date);
date_part
---------
        1
(1 row)

darcy=>\q


At 10:17 AM 4/3/01 -0400, Tom Lane wrote:
>Philip Warner <pjw@rhyme.com.au> writes:
>> At 00:59 3/04/01 -0400, Tom Lane wrote:
>>> However, the horology diffs are not, and I can't reproduce them here.
>>> Did anyone else see that?
>
>> I've just started seeing both...
>
>What is the date of the nearest daylight-savings transition in your
>timezone?
>
>Wait a minute ... considering that the regress tests run in PST8PDT,
>your local timezone shouldn't make a difference.  Maybe a platform-
>specific issue?  What platform (esp. which C library) do you use?
>
>FWIW, as of this morning I'm back to no failure on timestamp test
>(as expected), and still no horology failure either.
>
>            regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
>    (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
>

pgsql-bugs by date:

Previous
From: pgsql-bugs@postgresql.org
Date:
Subject: to_char miscalculation on April Fool's Day, the start of daylight savings
Next
From: Tom Lane
Date:
Subject: Re: Table constraint ordering disrupted by pg_dump