Message-ID: <501C179C.7020707@shopzeus.com>
Date: Fri, 03 Aug 2012 20:25:32 +0200
From: Laszlo Nagy <gandalf@shopzeus.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: pgsql-admin@postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Messed up time zones
References: <501B8C6F.6040100@shopzeus.com> <501BAA84.9010306@shopzeus.com>
	<501BAE33.4090102@shopzeus.com> <16399.1344003584@sss.pgh.pa.us>
	<501BED07.5070603@shopzeus.com> <501BEF7C.1030403@dhs-club.com>
	<501BF70E.4090903@shopzeus.com> <19252.1344011891@sss.pgh.pa.us>
In-Reply-To: <19252.1344011891@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit

 > [ shrug... ] If you really insist on re-inventing that wheel, go 
ahead, but it sounds to me like you'll just be introducing additional 
points of failure. regards, tom lane

I just checked some programming languages (Python, C#), and the same 
problem exists there. All of them say that "when the time is ambiguous, 
then it is assumed to be in standard time". So the representation is 
ambiguous in various programming languages too. You are right - it would 
be reinventing the wheel.

Although I don't like the fact that we are using an ambiguous system for 
measuring time, after all the problem was in my head.  I'm sorry for 
being hardheaded.