regression failure on master with --disable-integer-datetimes - Mailing list pgsql-bugs

From Jeff Davis
Subject regression failure on master with --disable-integer-datetimes
Date
Msg-id 1399399313.27807.28.camel@sussancws0025
Whole thread Raw
Responses Re: regression failure on master with --disable-integer-datetimes
List 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

pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: BUG #9635: Wal sender process is using 100% CPU
Next
From: Tom Lane
Date:
Subject: Re: regression failure on master with --disable-integer-datetimes