Folks,
Found this interesting bug:
jwnet=> select version();
version
---------------------------------------------------------------
PostgreSQL 7.2.1 on i686-pc-linux-gnu, compiled by GCC 2.95.3
(1 row)
jwnet=> select ('2001-07-31 10:00:00 PST'::TIMESTAMP) + ('248 days'::INTERVAL)
;
?column?
------------------------
2002-04-05 10:00:00-08
(1 row)
jwnet=> select ('2001-07-31 10:00:00 PST'::TIMESTAMP) + ('249 days'::INTERVAL)
;
?column?
------------------------
2002-04-06 10:00:00-08
(1 row)
jwnet=> select ('2001-07-31 10:00:00 PST'::TIMESTAMP) + ('250 days'::INTERVAL)
;
?column?
------------------------
2002-04-07 11:00:00-07
jwnet=> select ('2001-04-01 10:00:00 PST'::TIMESTAMP) + ('100 days'::INTERVAL)
;
?column?
------------------------
2001-07-10 11:00:00-07
It appears that Spring Daylight Savings Time causes PostgreSQL to change my
time zone. Only the spring, mind you, and not the fall. This is
potentially catastrophic for the application I'm developing; what can I do to
see that it's fixed? Or am I misunderstanding the behavior, here?
--
-Josh Berkus
P.S. I'm posting this here instead of the online bug form because I know that
Bruce is on vacation.
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
