From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Richard Huxton <dev(at)archonet(dot)com> |
Cc: | stevegy(at)126(dot)com, pgsql-general(at)postgresql(dot)org |
Subject: | Re: The jdbc and current_timestamp |
Date: | 2007-01-17 14:38:51 |
Message-ID: | 9103.1169044731@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Richard Huxton <dev(at)archonet(dot)com> writes:
> The time is fixed at the start of the transaction. This lets you do
> several inserts having the same timestamp.
I think there's another problem here, which is that he's declared
"currenttime" as a timestamp without time zone, but the
CURRENT_TIMESTAMP function yields timestamp with time zone,
meaning there's a TimeZone-dependent conversion going on. It sounds
to me like there's a difference between the TimeZone setting between
his web app and his psql, leading to an hour's offset, plus a smaller
offset having to do with time-since-transaction-start.
> See here for details of timeofday() etc.
> http://www.postgresql.org/docs/8.2/static/functions-datetime.html#FUNCTIONS-DATETIME-CURRENT
And read the preceding chapter's discussion of the different datetime
data types.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | k.novo | 2007-01-17 14:52:49 | PostgreSQL and embedded PC with Compact Flash? |
Previous Message | Bill Moran | 2007-01-17 14:32:23 | Index bloat of 4x |