Обсуждение: regression failure with current
I have seen following regression failure with current(I cvs up'ed 10 minutes ago). Any thought? This is Linux kernel 2.4.22 with glibc 2.2.4. -- Tatsuo Ishii *** ./expected/horology.out Mon Sep 29 17:53:48 2003 --- ./results/horology.out Sun Oct 26 20:21:59 2003 *************** *** 583,595 **** SELECT (timestamp with time zone 'today' = (timestamp with time zone 'tomorrow' - interval '1 day')) as"True"; True ------ ! t (1 row) SELECT (timestamp with time zone 'tomorrow' = (timestamp with time zone 'yesterday' + interval '2 days')) as"True"; True ------ ! t (1 row) SELECT (timestamp with time zone 'tomorrow' > 'now') as "True"; --- 583,595 ---- SELECT (timestamp with time zone 'today' = (timestamp with time zone 'tomorrow' - interval '1 day')) as"True"; True ------ ! f (1 row) SELECT (timestamp with time zone 'tomorrow' = (timestamp with time zone 'yesterday' + interval '2 days')) as"True"; True ------ ! f (1 row) SELECT (timestamp with time zone 'tomorrow' > 'now') as "True"; *************** *** 836,842 **** + interval '02:01' AS time with time zone) AS time) AS "03:31:00"; 03:31:00 ---------- ! 03:31:00 (1 row) SELECT CAST(cast(date 'today' + time with time zone '03:30' --- 836,842 ---- + interval '02:01' AS time with time zone) AS time) AS "03:31:00"; 03:31:00 ---------- ! 02:31:00 (1 row) SELECT CAST(cast(date 'today' + time with time zone '03:30' ======================================================================
On Sun, Oct 26, 2003 at 08:27:52PM +0900, Tatsuo Ishii wrote: > I have seen following regression failure with current(I cvs up'ed 10 > minutes ago). Any thought? This is Linux kernel 2.4.22 with glibc > 2.2.4. Maybe the change of TZ (summer to winter time) tonight caused this. Kurt
Kurt Roeckx wrote: > On Sun, Oct 26, 2003 at 08:27:52PM +0900, Tatsuo Ishii wrote: > > I have seen following regression failure with current(I cvs up'ed 10 > > minutes ago). Any thought? This is Linux kernel 2.4.22 with glibc > > 2.2.4. > > Maybe the change of TZ (summer to winter time) tonight caused > this. Yes, I saw identical failures --- must be timezone. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania19073
Bruce Momjian <pgman@candle.pha.pa.us> writes: > Kurt Roeckx wrote: >> On Sun, Oct 26, 2003 at 08:27:52PM +0900, Tatsuo Ishii wrote: >>> I have seen following regression failure with current(I cvs up'ed 10 >>> minutes ago). Any thought? This is Linux kernel 2.4.22 with glibc >>> 2.2.4. >> >> Maybe the change of TZ (summer to winter time) tonight caused >> this. > Yes, I saw identical failures --- must be timezone. Sheesh guys, "the horology tests fail at DST boundaries" is not only ancient project folklore, but is well documented: http://www.postgresql.org/docs/7.3/static/regress-evaluation.html#AEN23380 saith : Some of the queries in the horology test will fail if you run the test : on the day of a daylight-saving time changeover, or the day before or : after one. These queries assume that the intervals between midnight : yesterday, midnight today and midnight tomorrow are exactly : twenty-four hours -- which is wrong if daylight-saving time went into : or out of effect meanwhile. I could understand some newbie making these complaints, but y'all have little excuse... regards, tom lane