From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Mike Christensen <mike(at)kitchenpc(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Perf differences between timestamp and timestamp with timezone |
Date: | 2009-06-16 01:52:39 |
Message-ID: | 200906160152.n5G1qd719240@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Mike Christensen wrote:
> Hi all -
>
> I'm considering changing all my "timestamp" columns to "timestamp with
> timezone" columns instead. The reason is I want to use UTC time for
> everything in the DB and on the web server, and only ever convert to local
> time on the client itself. I could use a timestamp and just "know" that the
> timezone is UTC, but npgsql seems to handle this a lot better (like set the
> "Kind" property to UTC, etc) if you have a timestamptz column type.
>
> I'm curious if there's any perf drawbacks to doing this, or would the only
> perf hit be if I were comparing timestamp with timestamptz and doing all
> sorts of casts and stuff. Thanks!
I don't think there is any measurable difference in the two data types,
and timestamptz is usually superior, as you have found.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Just Someone | 2009-06-16 01:53:00 | Re: Amazon EC2 | Any recent developments |
Previous Message | Mike Christensen | 2009-06-16 01:06:31 | Perf differences between timestamp and timestamp with timezone |