Re: range_agg() missing support for multirange inputs

Thanks for the feedback, David.

It’s interesting how some reports are replied to within minutes, though.
Not much time for voting.

On Tue, 07 Dec 2021 at 15:47, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:

> On Tue, Dec 7, 2021 at 6:32 AM Ian R. Campbell <
> ian(dot)campbell(at)thepathcentral(dot)com> wrote:
>
>> *Moderator:* I have submitted this bug report twice, but it has never
>> made it onto the forum and I've never had feedback on it.
>>
>>
> I'm not a moderator but I can say that both your posts made it to the
> mailing list (or at least its archive...):
>
>
> https://www.postgresql.org/message-id/JNZP275MB0737BDCCB3792619F1DF04128A8C9@JNZP275MB0737.ZAFP275.PROD.OUTLOOK.COM
>
> https://www.postgresql.org/message-id/CAOC8YUcOtAGscPa31ik8UEMzgn8uAWA09s6CYOGPyP9_cBbWTw@mail.gmail.com
>
> The lack of feedback is unfortunate but it does happen since replies are
> up to individuals to decide to make.
>
> Going from memory at the moment, but I seem to recall this indeed being a
> missing behavior for this feature that wasn't caught before feature
> freeze. It is likely to be fixed for v15 but for v14 it is a missing
> feature. A search of the archives will turn up additional discussion on
> this should you wish a more detailed understanding.
>
> David J.
>
>
>