| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Karsten Hilbert *EXTERN*" <Karsten(dot)Hilbert(at)gmx(dot)net>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Timestamp with and without timezone conversion confusion. |
| Date: | 2013-10-02 11:48:02 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B17C25FAA@ntex2010a.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rysdam | 2013-10-02 12:34:44 | partitioning for speed, but query planner ignores |
| Previous Message | Karsten Hilbert | 2013-10-02 11:21:08 | Re: Timestamp with and without timezone conversion confusion. |