Re: [BUGS] BUG #5808: Remove PgOleDB from Stack Builder
On Fri, Dec 31, 2010 at 4:01 AM, Aren Cambre wrote: > > The following bug has been logged online: > > Bug reference: 5808 > Logged by: Aren Cambre > Email address: a...@arencambre.com > PostgreSQL version: 9.0.2 > Operating system: Windows 7 32 bit > Description: Remove PgOleDB from Stack Builder > Details: > > Is it time to stop letting PgOleDB be an option with the Stack Builder? Per > http://pgfoundry.org/projects/oledb/, that hasn't been updated in >4.5 > years. That's eons in the tech world. Maybe, but packages are included based on their usefulness, not project activity. The OLEDB spec hasn't changed in years, so there may not be any reason to update the code if no bugs have been reported. Regards, Dave. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] Re: to_timestamp returns the incorrect result for the DST fall over time.
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,'-MM-DD HH24:MI:SS.MS')+ interval '1 hour' *
(extract(timezone from to_timestamp($1,'-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.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] Re: to_timestamp returns the incorrect result for the DST fall over time.
On Wed, Jan 5, 2011 at 6:10 AM, Gouse wrote:
> // snippet of the stored procedure...
> CREATE OR REPLACE FUNCTION wf_to_timestamp("varchar")
> RETURNS timestamptz AS
> $BODY$
> select to_timestamp($1,'-MM-DD HH24:MI:SS.MS')+ interval '1 hour' *
> (extract(timezone from to_timestamp($1,'-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'.
How about something like this:
create or replace function x(text) returns timestamptz as $$select
to_timestamp($1,'-MM-DD HH24:MI:SS.MS')$$ set timezone = 'UTC'
language sql;
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
