From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: extend pgbench expressions with functions |
Date: | 2016-01-28 09:31:42 |
Message-ID: | alpine.DEB.2.10.1601281016400.27415@sto |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>> I do not think that it is really worth fixing, but I will not prevent anyone
>> to fix it.
>
> I still think it does. Well, if there is consensus to address this one
> and optionally the other integer overflows even on back branches, I'll
> write a patch and let's call that a deal. This is not a problem from
> my side.
My point is just about the cost-benefit of fixing a low probability issue
that you can only encounter if you are looking for it, and not with any
reasonable bench script.
Now adding somewhere a test might just help closing the subject and
do more useful things, so that would also be a win.
/* these would raise an arithmetic error */
if (lval == INT64_MIN && rval == -1)
{
fprintf(stderr, "cannot divide or modulo INT64_MIN by -1\n");
return false;
}
This may be backpatched to old supported versions.
--
Fabien.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2016-01-28 10:06:24 | Re: Template for commit messages |
Previous Message | Alvaro Herrera | 2016-01-28 09:15:28 | Re: Minor code improvements to create_foreignscan_plan/ExecInitForeignScan |