Re: extend pgbench expressions with functions

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: extend pgbench expressions with functions
Date: 2016-01-29 12:29:54
Message-ID: CAB7nPqSwBvUh9=k2RS_msD+=M99-sPWAb4vr2x9hZqykbKr0YQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jan 29, 2016 at 6:05 PM, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> wrote:
> (instead of < in my previous suggestion, if some processors return 0 on
> -INT64_MIN). Also, a comment is needed to explain why such a bizarre
> condition is used/needed for just the INT64_MIN case.

The last patch I sent has this bit:
+ /*
+ * Some machines throw a floating-point exception
+ * for INT64_MIN % -1, the correct answer being
+ * zero in any case.
+ */
How would you reformulate that à-la-Fabien?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Artur Zakirov 2016-01-29 12:42:38 Re: Mac OS: invalid byte sequence for encoding "UTF8"
Previous Message Michael Paquier 2016-01-29 12:13:09 Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby