Re: possible time change issue - known problem?

From: Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk>
To: Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dan Langille <dan(at)langille(dot)org>, pgsql-general(at)postgresql(dot)org
Subject: Re: possible time change issue - known problem?
Date: 2003-04-07 21:11:53
Message-ID: 20030407221153.A7521@quartz.newn.cam.ac.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Apr 07, 2003 at 08:42:56PM +0100, Patrick Welche wrote:
>
> *** ./expected/horology.out Mon Apr 7 16:56:14 2003
> --- ./results/horology.out Mon Apr 7 20:21:10 2003
> ***************
> *** 571,577 ****
> SELECT (timestamp with time zone 'today' = (timestamp with time zone 'yesterday' + interval '1 day')) as "True";
> True
> ------
> ! t
> (1 row)

Now for a mystery: I actually installed said postgres even though it failed
the regression test, and

template1=# SELECT (timestamp with time zone 'today' = (timestamp with time
template1(# zone 'tomorrow' - interval '1 day')) as "True";
True
------
t
(1 row)

gmake runcheck still fails horology(!)

Got it! We (Britain) changed time last week => it passes when I run the newly
installed database, whereas the regression test happens in PST8PDT, and I
believe you change time this weekend!

Sorry,

Patrick

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dan Langille 2003-04-07 21:14:54 Re: possible time change issue - known problem?
Previous Message Raymond O'Donnell 2003-04-07 21:04:42 Re: Consecutive queries