Re: Timestamp with and without timezone conversion confusion. - Mailing list pgsql-general

From Albe Laurenz
Subject Re: Timestamp with and without timezone conversion confusion.
Date
Msg-id A737B7A37273E048B164557ADEF4A58B17C25FAA@ntex2010a.host.magwien.gv.at
Whole thread Raw
In response to Re: Timestamp with and without timezone conversion confusion.  (Karsten Hilbert <Karsten.Hilbert@gmx.net>)
Responses Re: Timestamp with and without timezone conversion confusion.
List pgsql-general
Karsten Hilbert wrote:
> > > Maybe the question I need to ask is "how can I store the time zone along with the timestamp"
> >
> > Store an additional field "offset".
> > If you want to invest more energy and don't mind writing C,
> > you could create your own data type.
> 
> Might not a composite type (timestamp without timezone, interval) suffice ?

Depends on what you want.

If all you want is store timestamp and time zone, a composite
type is fine.

> Or does that still need some C sprinkling (for operator support, say) ?

Exactly. If you want "<" to work right for this data type
that's the road you have to go.

Yours,
Laurenz Albe

pgsql-general by date:

Previous
From: Karsten Hilbert
Date:
Subject: Re: Timestamp with and without timezone conversion confusion.
Next
From: David Rysdam
Date:
Subject: partitioning for speed, but query planner ignores