eshkin...@gmail.com writes:
> set timezone to 'W-SU'; select '2011-03-27 23:00:00'::timestamptz;
> SET
> timestamptz
>
> 2011-03-28 02:59:54+04
I've applied a patch for this. Thanks for the report!
regards, tom lane
--
Sent via pg
On 22/04/12 05:49, Tom Lane wrote:
eshkin...@gmail.com writes:
set timezone to 'W-SU'; select '2011-03-27 23:00:00'::timestamptz;
SET
timestamptz
2011-03-28 02:59:54+04
Bizarre. On my Fedora 16 box, I see a different misbehavior:
regression=# set timezone to
Jochen Erwied writes:
> Saturday, April 21, 2012, 7:49:55 PM you wrote:
>> So: some platform-specific misbehavior here. I have no time to poke at
>> it more now, though. Who else can reproduce this, on what platforms?
> One machine works, the other not:
I traced though it far enough to find th
Saturday, April 21, 2012, 7:49:55 PM you wrote:
> So: some platform-specific misbehavior here. I have no time to poke at
> it more now, though. Who else can reproduce this, on what platforms?
One machine works, the other not:
PostgreSQL 9.1.3 on i686-pc-linux-gnu, compiled by i686-pc-linux-gnu
> Tom Lane wrote:
> eshkin...@gmail.com writes:
>> set timezone to 'W-SU'; select '2011-03-27 23:00:00'::timestamptz;
>> SET
>> timestamptz
>>
>> 2011-03-28 02:59:54+04
>
> Bizarre. On my Fedora 16 box, I see a different misbehavior:
>
> regression=# set timezone to 'Eur
eshkin...@gmail.com writes:
> set timezone to 'W-SU'; select '2011-03-27 23:00:00'::timestamptz;
> SET
> timestamptz
>
> 2011-03-28 02:59:54+04
Bizarre. On my Fedora 16 box, I see a different misbehavior:
regression=# set timezone to 'Europe/Moscow'; selec
The following bug has been logged on the website:
Bug reference: 6605
Logged by: Sergey Burladyan
Email address: eshkin...@gmail.com
PostgreSQL version: 9.1.3
Operating system: Debian testing
Description:
Postgres from Debian package:
PostgreSQL 9.1.3 on x86_64-unknow
