BUG #5728: Unexpected behavior comparing result of age() to an interval - Mailing list pgsql-bugs

From Dobes Vandermeer
Subject BUG #5728: Unexpected behavior comparing result of age() to an interval
Date
Msg-id 201010262145.o9QLjZ2k097528@wwwmaster.postgresql.org
Whole thread Raw
Responses Re: BUG #5728: Unexpected behavior comparing result of age() to an interval  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
The following bug has been logged online:

Bug reference:      5728
Logged by:          Dobes Vandermeer
Email address:      dobes.vandermeer@kashoo.com
PostgreSQL version: 8.4
Operating system:   Windows
Description:        Unexpected behavior comparing result of age() to an
interval
Details:

Seeing some surprising behavior with the use of age() and comparing the
result to an interval:

select current_date,
       age(current_date - interval '123 days') <= interval '120 days',
       age(current_date - interval '122 days') <= interval '120 days',
       age(current_date - interval '121 days') <= interval '120 days',
       age(current_date - interval '120 days') <= interval '120 days',
       age(current_date - interval '62 days') <= interval '60 days',
       age(current_date - interval '61 days') <= interval '60 days',
       age(current_date - interval '60 days') <= interval '60 days',
       age(current_date - interval '30 days') <= interval '30 days';


Returns:

"2010-10-26";f;t;t;t;f;t;t;t

But I expected:

"2010-10-26";f;f;f;t;f;f;t;t

Something fishy there ...

pgsql-bugs by date:

Previous
From: Simon Riggs
Date:
Subject: Re: BUG #5727: Indexes broken in streaming replication
Next
From: Tom Lane
Date:
Subject: Re: BUG #5728: Unexpected behavior comparing result of age() to an interval