| From: | Mike Christensen <mike(at)kitchenpc(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Perf differences between timestamp and timestamp with timezone |
| Date: | 2009-06-16 01:06:31 |
| Message-ID: | 7aa638e00906151806s653a991fl3a669c047fac4947@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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!
Mike
PS - If there's any way to make npgsql just manufacture UTC DateTime objects
to begin with, that would be nice too.. Digging through the code I coudn't
find an easy way.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2009-06-16 01:52:39 | Re: Perf differences between timestamp and timestamp with timezone |
| Previous Message | gvimrc | 2009-06-16 00:16:19 | pl/sql resources for pl/pgsql? |