Re: range_agg - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: range_agg
Date
Msg-id cdd809b0869d3bb334e68ed9ebdd1d3f97289338.camel@j-davis.com
Whole thread Raw
In response to Re: range_agg  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: range_agg  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On Fri, 2019-07-05 at 07:58 +0200, Pavel Stehule wrote:
> The question is naming - should be this agg function named
> "range_agg", and multi range agg "multirange_agg"? Personally, I have
> not a problem with range_agg, and I have not a problem so it is based
> on union operation. It is true so only result of union can be
> implemented as range simply. When I though about multi range result,
> then there are really large set of possible algorithms how to do some
> operations over two, three values.

Hi Pavel,

Can you explain in more detail? Would an intersection-based aggregate
be useful? If so, and we implement it in the future, what would we call
it?

Regards,
    Jeff Davis





pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH v4] Add \warn to psql
Next
From: Paul A Jungwirth
Date:
Subject: Re: range_agg