Re: [HACKERS] New pgbench functions are misnamed

Robert Haas writes: > On Wed, May 4, 2016 at 5:41 PM, Tom Lane wrote: >> I noticed that commit 7e137f846 added functions named max() and min() >> to pgbench's expression syntax. Unfortunately, these functions have >> zilch to do with what max() and

Re: [HACKERS] New pgbench functions are misnamed

I noticed that commit 7e137f846 added functions named max() and min() to pgbench's expression syntax. Unfortunately, these functions have zilch to do with what max() and min() do in SQL. They're actually more like the greatest() and least() server-side functions. Yep. While I can't imagine

Re: [HACKERS] New pgbench functions are misnamed

On Wed, May 4, 2016 at 5:41 PM, Tom Lane wrote: > I noticed that commit 7e137f846 added functions named max() and min() > to pgbench's expression syntax. Unfortunately, these functions have > zilch to do with what max() and min() do in SQL. They're actually more > like the

[HACKERS] New pgbench functions are misnamed

I noticed that commit 7e137f846 added functions named max() and min() to pgbench's expression syntax. Unfortunately, these functions have zilch to do with what max() and min() do in SQL. They're actually more like the greatest() and least() server-side functions. While I can't imagine that we'd