Thanks Tom for the Update.
You are correct that there is not local date and time for that DST time
period as clocks jump to 2 A.M.
The problem i am seeing here is that, we have a small stored procedure
written which will always take UTC time as parameter and should convert it
to local timestamp with time zone. Can you verify the sp pls and let me if I
am doing something wrong.
// snippet of the stored procedure...
CREATE OR REPLACE FUNCTION wf_to_timestamp("varchar")
RETURNS timestamptz AS
$BODY$
select to_timestamp($1,'YYYY-MM-DD HH24:MI:SS.MS')+ interval '1 hour' *
(extract(timezone from to_timestamp($1,'YYYY-MM-DD HH24:MI:SS.MS')) /
3600.0)
$BODY$
LANGUAGE 'sql' VOLATILE;
ALTER FUNCTION wf_to_timestamp("varchar") OWNER TO postgres;
When I pass the UTC time '2010-03-28 01:00:03 243' I should expect the
output to be '2010-03-28 02:00:03.243 + 01' , instead I am getting the
result '2010-03-28 03:00:03.243 + 01'.
The store procedure works well for the UTC time starting from '2010-03-28
02:00:00 000'. The problem only lies for the UTC time period from
'2010-03-28 01:00:00 000' to '2010-03-28 01:59:59 999'.
Can you verifiy this pls..?
Thanks,
Gouse
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/to-timestamp-returns-the-incorrect-result-for-the-DST-fall-over-time-tp3327393p3328589.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
