You are both right.
Your explanation, Steve, was the light that got me going on a simpler
solution along the lines of what Tom suggested. I didn't really need
AGE, and upon digging in, couldn't even remember why I had chosen that
in the first place.
Postgres is the bomb!
Thanks guys.
Steve Crawford wrote:
>
> On Wednesday 03 March 2004 3:19 pm, Tom Lane wrote:
> > Steve Crawford <scrawford@pinpointresearch.com> writes:
> > > US Daylight Saving Time starts this year on April 4 when 0200
> > > jumps to 0300. The answers PostgreSQL gave are correct.
> >
> > I suspect what the OP wants is non-timezone-aware behavior...
>
> You are probably right. In his original post he posited that the
> problem was due to some sort of leap-year bug in PostgreSQL. I was
> just pointing him to the real cause of his observations so he could
> tackle whatever problem he was having secure in the knowledge that PG
> was working correctly.
>
> Cheers,
> Steve
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
--
Bill MacArthur
Webmaster
The DHS Club, Inc.
The Best Is Yet To Come!