[HACKERS] regression failure with current

[Tatsuo Ishii]

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'

======================================================================



---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match