Re: timestamps cannot be created without time zones

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Rainer Mager <rmager(at)vgkk(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: timestamps cannot be created without time zones
Date: 2001-08-24 20:02:09
Message-ID: 200108242002.f7OK29323416@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Bruce Momjian writes:
> >> Let me see if I follow here. If I am in the Eastern timezone and enter
> >> a time for 9pm, 1/1/1850, and someone else in the Central timezone
> >> enters the same time, if I look at the two dates from the Eastern
> >> timezone I will see mine as 9pm and the other as 10pm?
>
> > That's exactly what happens, only that the central time would probably
> > show 8pm.
>
> No, that is *not* what happens. For dates outside the range known to
> the local platform's timezone database, we effectively assume that all
> times are given in GMT; no timezone corrections are applied on either
> input or output. For example:

Nifty trick. :-)

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David Daney 2001-08-24 21:16:14 Re: [BUGS] Bug #428: Another security issue with the JDBC driver.
Previous Message Tom Lane 2001-08-24 20:00:59 Re: Re: Strange deadlock problem on simple concurrent SELECT/LOCK TABLE transactions