Re: range_agg - Mailing list pgsql-hackers

From Paul A Jungwirth
Subject Re: range_agg
Date
Msg-id CA+renyWzGGq38iv_hD4OE7AfHbxLJOtHAMtit=axJw6QdjdVQg@mail.gmail.com
Whole thread Raw
In response to Re: range_agg  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: range_agg  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, Jan 19, 2020 at 12:10 AM Pavel Stehule <pavel.stehule@gmail.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



pgsql-hackers by date:

Previous
From: Ranier Vilela
Date:
Subject: [PATCH] src\backend\utils\adt\numeric.c copy and past error
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] src\backend\utils\adt\numeric.c copy and past error