| From: | Paul Jungwirth <pj(at)illuminatedcomputing(dot)com> |
|---|---|
| To: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Subject: | range_agg with multirange inputs |
| Date: | 2021-12-11 00:24:48 |
| Message-ID: | 007ef255-35ef-fd26-679c-f97e7a7f30c2@illuminatedcomputing.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Here is a patch adding range_agg(anymultirange). Previously range_agg
only accepted anyrange.
Here is a bug report from last month requesting this addition:
As that message points out, range_intersect_agg accepts either anyrange
or anymultirange, so it makes sense for range_agg to do the same.
I noticed that the docs only mentioned range_intersect_agg(anyrange), so
I added the anymultirange versions of both on the aggregate functions page.
I also added a few more tests for range_intersect_agg since the coverage
there seemed light.
Yours,
--
Paul ~{:-)
pj(at)illuminatedcomputing(dot)com
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Add-range_agg-with-multirange-inputs.patch | text/x-patch | 12.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2021-12-11 01:20:52 | isolationtester: add session name to application name |
| Previous Message | Andres Freund | 2021-12-11 00:17:19 | Re: A test for replay of regression tests |