Re: Best practices: Handling Daylight-saving time

From: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Best practices: Handling Daylight-saving time
Date: 2005-03-12 22:10:17
Message-ID: 20050312231017.W565@hermes.hilbert.loc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, Mar 12, 2005 at 12:22:38PM -0500, Randall Nortman wrote:
>
> Anyway, afaik, Postgres does not store the "original" timezone
> anywhere, and so could not possibly retrieve it. I think the only
> physical difference between the "timestamp" and "timestamp with time
> zone" types is in the system catalog; the manual states that both of
> them store 8 bytes and have the same range. If "timestamp with time
> zone" were storing anything extra, I would think the storage size
> would be greater or else the range smaller.
Am I correct to assume that this could be solved with a user
defined composite data type ? From the docs it so seems.

Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2005-03-12 23:18:39 Re: partitionning
Previous Message Bruce Momjian 2005-03-12 21:57:27 Re: Moving an object (function/table, etc) from schema to