On Wed, Mar 30, 2016 at 10:13 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Michael Paquier <michael.paqu...@gmail.com> writes: >> On Wed, Mar 30, 2016 at 6:09 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: >>> Allow to_timestamp(float8) to convert float infinity to timestamp infinity. > >> Some of the tests introduced are making MSVC unhappy, because they >> depend on the three-digit behavior that Windows is using, leading to >> those failures: > > Ah, I was wondering about that. The patch as-submitted used "%lf" which > seemed even less likely to be portable, but evidently %g isn't that much > better.
Yep. >> If the those tests are kept, an alternate output file is necessary (I >> can send a patch if needed, I see the failure locally as well). > > I'm inclined to just drop the out-of-range test cases. They're not that > useful IMO, and alternate expected-files are a real PITA for maintenance. Hm. Actually, they are quite useful to check error boundaries, so why not just simplifying the error message to "timestamp out of range" and remove the value from it? -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
