Re: Timestamp operator error

Tom,

> AFAICT, what's happening in 7.2 is that the closest-match operator
> is "time + date", so it casts the interval to time (yielding 0
> hours),
> and casts current_timestamp to date (yielding midnight today)
> and adds.

Any suggestions on an emergency fix for my (production) database?
We've already seen a couple of major problems from this bug, and I'm
worried that there will be others that I don't catch until it's too
late. If I had the know-how, I'd fix the operator myself, but I
don't.

> I suspect this is good ammunition for the argument I've made from
> time
> to time that we have too many implicit conversions, not too few.

Yes, definitely. Frankly, I'd prefer a large reduction in implicit
conversions; I just got into trouble with the difference between
current_timestamp and current_date that I would have caught much
earlier if Postgres had disallowed the implicit conversion.

-Josh

______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh(at)agliodbs(dot)com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco