Received: from maia.hub.org (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id EA9E5633BB8
	for <pgsql-sql-postgresql.org@mail.postgresql.org>;
	Fri,  5 Mar 2010 07:46:14 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia,
	port 10024) with ESMTP id 17923-05 for
	<pgsql-sql-postgresql.org@mail.postgresql.org>;
	Fri,  5 Mar 2010 11:46:04 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from moon.antora.ru (moon.antora.ru [89.111.189.180])
	by mail.postgresql.org (Postfix) with ESMTP id 69D94633575
	for <pgsql-sql@postgresql.org>; Fri,  5 Mar 2010 07:46:04 -0400 (AST)
Envelope-to: pgsql-sql@postgresql.org
Received: from moon.inner.space ([10.1.1.5] helo=moon.antora.ru)
	by moon.antora.ru with esmtp (Exim 4.67)
	(envelope-from <sad@bankir.ru>) id 1NnVyh-0002Bd-Mg
	for pgsql-sql@postgresql.org; Fri, 05 Mar 2010 14:45:59 +0300
Received: from [192.168.1.107] [85.172.11.247] by moon.antora.ru (Axigen)
	with (DHE-RSA-AES256-SHA encrypted) ESMTPSA id 0E1D2B;
	Fri, 5 Mar 2010 14:45:59 +0300
Message-ID: <4B90EEBD.8070100@bankir.ru>
Date: Fri, 05 Mar 2010 14:45:01 +0300
From: silly sad <sad@bankir.ru>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5)
	Gecko/20100111 Thunderbird/3.0
MIME-Version: 1.0
To: pgsql-sql@postgresql.org
Subject: client_timezone to server_timezone and reverse
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scan-Signature: 2a1ad7a1f2b660e4ce39e359d87e6433
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.11 tagged_above=-10 required=5 tests=BAYES_05=-1.11
X-Spam-Level: 
X-Archive-Number: 201003/36
X-Sequence-Number: 33743

HELO

i am looking for strange things:
a timezone conversion AS transparent AS a charset encoding conversion are.

for __example__ (not intending to override the current behavior)

i want to see now()::timestampTZ always the same
(the server side time with the timezone predefined firmly)

and to see now()::timeztamp calculated according to the client_timezone 
setting whatever the user set it to.

In addition to the current behavior it whould be NICE to
cast timestamTZ to timestamp taking in account a shift between server 
and client time, if client specified his TZ.