From: | Florian Weimer <fweimer(at)bfk(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Agent M <agentm(at)themactionfaction(dot)com>, Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Timestamp vs timestamptz |
Date: | 2006-07-14 15:31:38 |
Message-ID: | 82wtag42zp.fsf@mid.bfk.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
* Tom Lane:
> Florian Weimer <fweimer(at)bfk(dot)de> writes:
>> * Agent M.:
>>> timestamp with time zone does not record the timezone you inserted it
>>> with- it simply stores the GMT version and converts to whatever
>>> timezone you like on demand.
>
>> Are you sure? This behavior is not documented, and I can't reproduce
>> it with PostgresQL 8.1.4.
>
> Huh? Section 8.5.1.3. Time Stamps says
Oops, I misread what Agent M wrote--"timestamp with time zone" vs
"timestamp with time zone". Sorry about that.
--
Florian Weimer <fweimer(at)bfk(dot)de>
BFK edv-consulting GmbH http://www.bfk.de/
Durlacher Allee 47 tel: +49-721-96201-1
D-76131 Karlsruhe fax: +49-721-96201-99
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-07-14 15:36:23 | Re: Q: Table scans on set difference |
Previous Message | Merlin Moncure | 2006-07-14 15:29:15 | Re: Is there a way to run tables in RAM? |