| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: extend pgbench expressions with functions |
| Date: | 2015-12-17 13:33:12 |
| Message-ID: | alpine.DEB.2.10.1512171409310.8362@sto |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> (2a) remove double stuff, just keep integer functions.
>> I would rather keep min/max, though.
>
> (2a) sounds like a fine plan to get something committable. We could keep
> min/max/abs, and remove sqrt/pi. What's actually the use case for debug?
> I cannot wrap my mind on one?
It was definitely useful to debug the double/int type stuff within
expressions when writing a non trivial pgbench script. It is probably less
interesting if there are only integers.
>> (2b) keep the patch with both int & double as is.
>
> Functions returning double are not that useful... pgbench can live
> without them.
Sure.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2015-12-17 14:32:18 | Re: parallel joins, and better parallel explain |
| Previous Message | David Rowley | 2015-12-17 13:17:20 | Re: Performance improvement for joins where outer side is unique |