Re: [HACKERS] pow support for pgbench - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] pow support for pgbench
Date
Msg-id CAB7nPqRM41eZYZT18J52H1WR2HSbwhLvpwOJQm563nZSv0-UTA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] pow support for pgbench  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Dec 5, 2017 at 11:32 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> ISTM one key issue here is whether pgbench's expression language is
> meant to model SQL (where we have function overloading) or C (where
> there is no overloading).  I don't think we've really settled on a
> fixed policy on that, but maybe now is the time.

abs() is doing that already. Having some rules in the shape of at
least a comment would be nice.

> If we do think that function overloading is OK, there remains the
> question of when the typing is resolved.  I think Robert is objecting
> to resolving at runtime, and I tend to agree that that's something
> we'd regret in the long run.  It doesn't match either SQL or C.

+1.
-- 
Michael


pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Usage of epoch in txid_current
Next
From: Craig Ringer
Date:
Subject: Re: [HACKERS] logical decoding of two-phase transactions