Date: Wed, 12 Feb 2014 00:24:15 -0800 (PST)
From: rawi <only4com@web.de>
To: pgsql-sql@postgresql.org
Message-ID: <1392193455856-5791556.post@n5.nabble.com>
In-Reply-To: <52FA3499.3020604@gmail.com>
References: <1392105285704-5791371.post@n5.nabble.com>
 <52FA3499.3020604@gmail.com>
Subject: Re: Time AT TIME ZONE: false result using offset instead of time
 zone name
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

Adrian Klaver-3 wrote
>>On 02/10/2014 11:54 PM, rawi wrote:
>>[...]
>> SELECT CURRENT_TIMESTAMP AT TIME ZONE 'UTC+01';
>>
>> timezone
>> timestamp without time zone
>> ---------------------------
>> 2014-02-11 06:23:07.043479
>>
>> !!! Two hours earlyer, one hour to the east (Azores), not to the west of
>> Greenwich.
>> To get my time one hour west from Greenwich I have to ask:
>>
>> SELECT CURRENT_TIMESTAMP AT TIME ZONE 'UTC-01';
>>
>> Is this inverse calculation intently?
> 
> Yes.
> 
> http://www.postgresql.org/docs/9.3/interactive/datatype-datetime.html#DATATYPE-TIMEZONES
> 
> 8.5.3. Time Zones
> 
> .. Another issue to keep in mind is that in POSIX time zone names, 
> positive offsets are used for locations west of Greenwich. Everywhere 
> else, PostgreSQL follows the ISO-8601 convention that positive timezone 
> offsets are east of Greenwich

Oh... oh... Disconcerting... I've just learned, that even javascript is
returning negative offsets for western situated browsers...

Thank you!
Regards, Rawi


--
View this message in context: http://postgresql.1045698.n5.nabble.com/Time-AT-TIME-ZONE-false-result-using-offset-instead-of-time-zone-name-tp5791371p5791556.html
Sent from the PostgreSQL - sql mailing list archive at Nabble.com.


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql