| From: | Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: range_agg |
| Date: | 2020-01-19 23:34:25 |
| Message-ID: | CA+renyWzGGq38iv_hD4OE7AfHbxLJOtHAMtit=axJw6QdjdVQg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jan 19, 2020 at 12:10 AM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> Now, I think so name "anymultirange" is not good. Maybe better name is just "multirange"
Are you sure? This function exists to be a cast to an anymultirange,
and I thought the convention was to name cast functions after their
destination type. I can change it, but in my opinion anymultirange
follows the Postgres conventions better. But just let me know and I'll
do "multirange" instead!
Yours,
Paul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-01-20 00:22:48 | Re: [PATCH] src\backend\utils\adt\numeric.c copy and past error |
| Previous Message | Ranier Vilela | 2020-01-19 23:11:56 | [PATCH] src\backend\utils\adt\numeric.c copy and past error |