Re: range_agg with multirange inputs

2022-03-30 Thread Peter Eisentraut
This patch has been committed. I split it into a few pieces. On 12.03.22 04:18, Paul Jungwirth wrote: On 3/10/22 14:07, Chapman Flack wrote: When I apply this patch, I get a func.sgml with two entries for range_intersect_agg(anymultirange). Arg, fixed. In range_agg_transfn, you've changed

Re: range_agg with multirange inputs

2022-03-28 Thread Greg Stark
Fwiw the cfbot is failing due to a duplicate OID. Traditionally we didn't treat duplicate OIDs as reason to reject a patch because they're inevitable as other patches get committed and the committer can just renumber them. I think the cfbot kind of changes this calculus since it's a pain lose the

Re: range_agg with multirange inputs

2022-03-12 Thread Chapman Flack
On 03/11/22 22:18, Paul Jungwirth wrote: > Arg, fixed. > >> In range_agg_transfn, you've changed the message in the "must be called >> with a range or multirange"; that seems like another good candidate to >> be an elog. > > Agreed. Updated here. This looks good to me and passes

Re: range_agg with multirange inputs

2022-03-11 Thread Paul Jungwirth
or so many iterations! :-) Yours, -- Paul ~{:-) p...@illuminatedcomputing.comFrom b409d7333132e34a928ec8cc0ecca0a3421b7268 Mon Sep 17 00:00:00 2001 From: "Paul A. Jungwirth" Date: Fri, 10 Dec 2021 16:04:57 -0800 Subject: [PATCH v4] Add range_agg with multirange inputs --- do

Re: range_agg with multirange inputs

2022-03-10 Thread Chapman Flack
On 03/05/22 15:53, Paul Jungwirth wrote: > On 3/1/22 13:33, Chapman Flack wrote: >> I think the 4 lines should suffice, but it looks like this patch was >> generated from a rebase of the old one (with three lines) that ended up >> putting the new 'range_agg' entry ahead of 'max' in func.sgml,

Re: range_agg with multirange inputs

2022-03-05 Thread Paul Jungwirth
uting.comFrom 1e7a96668b0ad341d29281055927ad693c656843 Mon Sep 17 00:00:00 2001 From: "Paul A. Jungwirth" Date: Fri, 10 Dec 2021 16:04:57 -0800 Subject: [PATCH v3] Add range_agg with multirange inputs --- doc/src/sgml/func.sgml| 45 src/backend/utils/adt/multir

Re: range_agg with multirange inputs

2022-03-01 Thread Chapman Flack
On 02/28/22 23:31, Paul Jungwirth wrote: > On 2/26/22 17:13, Chapman Flack wrote: >> (I think generating >> the patch with 4 lines of context would be enough to keep that from being >> a recurring issue.) > > Thank you for the review and the tip re 4 lines of context! Rebase attached. I think

Re: range_agg with multirange inputs

2022-02-28 Thread Paul Jungwirth
change it? It seems like a worthwhile check in any case. Yours, -- Paul ~{:-) p...@illuminatedcomputing.comFrom a6689485aab9b1aaa6e866f2a577368c7a0e324e Mon Sep 17 00:00:00 2001 From: "Paul A. Jungwirth" Date: Fri, 10 Dec 2021 16:04:57 -0800 Subject: [PATCH v2] Add ra

Re: range_agg with multirange inputs

2022-02-26 Thread Chapman Flack
The following review has been posted through the commitfest application: make installcheck-world: tested, passed Implements feature: tested, passed Spec compliant: not tested Documentation:not tested This applies (with some fuzz) and passes installcheck-world, but a

range_agg with multirange inputs

2021-12-10 Thread Paul Jungwirth
/expected/multirangetypes.out index f5f089741c..7c91e3c5f2 100644 --- a/src/test/regress/expected/multirangetypes.out +++ b/src/test/regress/expected/multirangetypes.out @@ -2771,6 +2771,70 @@ FROM(VALUES {[a,f],[g,j)} (1 row) +-- range_agg with multirange inputs +select range_agg(nmr) fro