X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 6F4588BA342 for ; Mon, 21 Feb 2005 13:38:07 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 69077-03 for ; Mon, 21 Feb 2005 13:37:59 +0000 (GMT) Received: from matrix.gatewaynet.com (matrix.gatewaynet.com [217.19.69.50]) by svr1.postgresql.org (Postfix) with ESMTP id 70A5E8BA2FB for ; Mon, 21 Feb 2005 13:38:01 +0000 (GMT) Received: from matrix.gatewaynet.com (localhost.localdomain [127.0.0.1]) by matrix.gatewaynet.com (8.12.8/8.12.8) with ESMTP id j1LEG41M007338 for ; Mon, 21 Feb 2005 16:16:04 +0200 Received: from localhost (achill@localhost) by matrix.gatewaynet.com (8.12.8/8.12.8/Submit) with ESMTP id j1LEG4iC007334 for ; Mon, 21 Feb 2005 16:16:04 +0200 Date: Mon, 21 Feb 2005 16:16:04 +0200 (EET) From: Achilleus Mantzios To: pgsql-sql@postgresql.org Subject: Timestamp with timezone question. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200502/222 X-Sequence-Number: 20333 AFAIK, the input for a timestamptz is converted and stored as UTC. And outputing a timezonetz value converts the internally stored UTC value to the current locale's timezone. So there is not a way to actually store the original TZ itself, whereas the timetz type clearly does that. Consider a schema designed to store internet mail. Since pgsql always converts a timestamptz to UTC, we have lost the information of the Sender's local timezone. Should i go with a separete date and timetz ? -- -Achilleus