regression failure on master with --disable-integer-datetimes

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Cc: Noah Misch <noah(at)leadboat(dot)com>
Subject: regression failure on master with --disable-integer-datetimes
Date: 2014-05-06 18:01:53
Message-ID: 1399399313.27807.28.camel@sussancws0025
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Introduced in commit 4318daecc959886d001a6e79c6ea853e8b1dfb4b.

Attached regression failure and patch. It looks like we're no longer
running floating point timestamps on the buildfarm?

To make the output for float/integer timestamps the same, we either need
to remove the fractional seconds or reduce the number of hours.

It looks like the test is for maximum output length of an interval, so
it seems better to reduce the number of hours to one million, which is
what my patch does. It still loses 3 characters of output length, which
is a bit unfortunate given the purpose of the test, but it's better than
losing 7. I don't have a better idea.

Regards,
Jeff Davis

Attachment Content-Type Size
regression.diffs text/x-patch 1.2 KB
float-test.patch text/x-patch 1.8 KB

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-05-06 18:48:31 Re: regression failure on master with --disable-integer-datetimes
Previous Message Heikki Linnakangas 2014-05-06 17:32:35 Re: BUG #9635: Wal sender process is using 100% CPU