| 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: | 2015-12-18 00:09:10 |
| Message-ID: | CAB7nPqRRXWvx=1_caFtr_7Ztx9P2-FTpkk0C5zMoL06y2ZZjeQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 18, 2015 at 9:08 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Thu, Dec 17, 2015 at 10:33 PM, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> wrote:
>>
>>>> (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.
>
> OK for me. Let's leave without it as well if you think it is not that
> useful. It could still be introduced later on.
s/leave/live. This morning is a bit hard...
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-12-18 01:07:55 | Re: Small fix in pg_rewind (redundant declaration) |
| Previous Message | Michael Paquier | 2015-12-18 00:08:48 | Re: extend pgbench expressions with functions |