Re: [HACKERS] Interval aggregate regression failure (expected seems - Mailing list pgsql-patches

From Michael Glaesemann
Subject Re: [HACKERS] Interval aggregate regression failure (expected seems
Date
Msg-id ED3C135A-9022-4655-AB8C-65658E2567D2@seespotcode.net
Whole thread Raw
In response to Re: [HACKERS] Interval aggregate regression failure (expected seems  (Michael Glaesemann <grzm@seespotcode.net>)
Responses Re: [HACKERS] Interval aggregate regression failure  (Bruce Momjian <bruce@momjian.us>)
List pgsql-patches
On Aug 29, 2006, at 15:38 , Michael Glaesemann wrote:

> I think I've got it. I plan to update the regression tests this
> evening, but I wanted to post what I believe is a solution.

I've cleaned up the patch a bit in terms of whitespace, comments, and
parens. I've also updated the interval and horology regression tests.
The horology tests needed updating because I added 5 rows to
INTERVAL_TBL. I didn't check the math for every row of time(tz |
stamp | stamptz)/interval arithmetic in the horology tests as I think
problems in this area would have shown up before. Does that make
sense or it just rationalization on my part?

Both with and without --enable-integer-datetimes pass the regression
tests.

Thanks!

Michael Glaesemann
grzm seespotcode net




Attachment

pgsql-patches by date:

Previous
From: "Guillaume Smet"
Date:
Subject: Re: [HACKERS] log_statement output for protocol
Next
From: Zoltan Boszormenyi
Date:
Subject: Re: [HACKERS] Performance testing of COPY (SELECT)