From: Laszlo Nagy <gandalf@shopzeus.com>
To: pgsql-admin@postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Messed up time zones
Date: Fri, 03 Aug 2012 20:25:32 +0200
Message-ID: <501C179C.7020707@shopzeus.com> (raw)
In-Reply-To: <19252.1344011891@sss.pgh.pa.us>
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>
> [ 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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: gandalf@shopzeus.com, tgl@sss.pgh.pa.us
Subject: Re: Messed up time zones
In-Reply-To: <501C179C.7020707@shopzeus.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox