Skip site navigation (1) Skip section navigation (2)

Re: BUG #6605: wrong type cast from timestamp to timestamptz

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jochen Erwied <jochen(at)pgsql-bugs(dot)erwied(dot)eu>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6605: wrong type cast from timestamp to timestamptz
Date: 2012-04-23 13:22:42
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Jochen Erwied <jochen(at)pgsql-bugs(dot)erwied(dot)eu> 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 that pg_next_dst_boundary indexes
off the end of an array when the given probe time is exactly the last
DST transition time for the zone.  So what's surprising is not that
it fails weirdly, but that there seem to be numerous machines where
it doesn't (appear to) fail.  The next array slot must chance to have
a sane value in some environments.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Kevin GrittnerDate: 2012-04-23 14:53:03
Subject: Re: BUG #6607: Strange select behavior
Previous:From: Matteo BeccatiDate: 2012-04-23 11:49:39

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group