From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | Wei Wei <wei725(at)lycos(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Calendar vs. Timestamp |
Date: | 2006-04-11 23:19:49 |
Message-ID: | Pine.BSO.4.63.0604111814090.31152@leary2.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Tue, 11 Apr 2006, Wei Wei wrote:
> I would like to clarify one observation. The timestamp seems only take
> the date section data of a calendar object regardless the value of the
> time zone. If so, a calendar object with a specified time zone would not
> make any difference in comparsion to a calendar object with the default
> time zone. Or, the default time zone is always used in PG.
>
I think the confusion arises from the fact that the server always stores
timestamps in utc and always returns them based upon the current setting
of the TimeZone configuration parameter.
CREATE TABLE tstest(a timestamptz);
INSERT INTO tstest VALUES ('2006-04-11 16:15:28-07');
INSERT INTO tstest VALUES ('2006-04-11 16:15:28-08');
SET TimeZone = 'America/Los_Angeles';
INSERT INTO tstest VALUES ('2006-04-11 16:15:28');
SELECT * FROM tstest;
SET TimeZone = 'America/New_York';
INSERT INTO tstest VALUES ('2006-04-11 16:15:28');
SELECT * FROM tstest;
Kris Jurka
From | Date | Subject | |
---|---|---|---|
Next Message | Wei Wei | 2006-04-11 23:53:55 | Re: Calendar vs. Timestamp |
Previous Message | Kris Jurka | 2006-04-11 22:59:33 | Re: FastPath blocked when ERROR is thrown |