Re: Best practices: Handling Daylight-saving time - Mailing list pgsql-general

From Karsten Hilbert
Subject Re: Best practices: Handling Daylight-saving time
Date
Msg-id 20050312231017.W565@hermes.hilbert.loc
Whole thread Raw
In response to Re: Best practices: Handling Daylight-saving time  (Randall Nortman <postgreslists@wonderclown.com>)
List 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

pgsql-general by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Moving an object (function/table, etc) from schema to
Next
From: Martijn van Oosterhout
Date:
Subject: Re: partitionning