Richard Huxton writes:
> The isn't '2009 ... +11', it's the absolute
> time that string represents. It doesn't in fact have a time-zone
> component except in the context of your locale settings.
> I don't know if we do follow the standard here though - not read it through.
The spec does appea
Albe Laurenz wrote:
Richard Huxton wrote:
test=> SELECT date_part('timezone_hours', timestamp with time zone '2009-06-26
10:05:57.46624+11');
I like your suggestion of "absolute time", which makes PostgreSQL's
timestamptz much easier to understand.
What worries me a bit is that the SQL stan
Richard Huxton wrote:
> > test=> SELECT date_part('timezone_hours', timestamp with time zone
> > '2009-06-26 10:05:57.46624+11');
> > date_part
> > ---
> > 2
> > (1 row)
> >
> > 2 being the offset of my local time zone.
> >
> > Now an EXPLAIN shows that this is due to the fact
Albe Laurenz wrote:
test=> SELECT date_part('timezone_hours', timestamp with time zone '2009-06-26
10:05:57.46624+11');
date_part
---
2
(1 row)
2 being the offset of my local time zone.
Now an EXPLAIN shows that this is due to the fact that the timestamp
is converted to my
