Re: [Django] #34078: Add Postgres range_merge aggregate function to postgres.contrib

[Django]

#34078: Add Postgres range_merge aggregate function to postgres.contrib
-------------------------------------+-------------------------------------
Reporter: Jack Linke | Owner: (none)
Type: New feature | Status: new
Component: contrib.postgres | Version: 4.1
Severity: Normal | Resolution:
Keywords: postgres range | Triage Stage:
range_merge aggregation aggregate | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Claude Paroz):

I think adding the `range_merge` function could be accepted in
contrib.postgres. However, what you suggest is to add a custom aggregate
(which is a different variant of the `range_agg`/`range_intersect_agg`
aggregations added in PostgreSQL 14). Therefore, my opinion is that your
custom aggregation is quite niche and could stay in a custom package.

--
Ticket URL: <https://code.djangoproject.com/ticket/34078#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#34078: Add Postgres range_merge aggregate function to postgres.contrib
-------------------------------------+-------------------------------------
Reporter: Jack Linke | Owner: (none)

Type: New feature | Status: closed
Component: contrib.postgres | Version: 4.1
Severity: Normal | Resolution: wontfix

Keywords: postgres range | Triage Stage:
range_merge aggregation aggregate | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Mariusz Felisiak):

* status: new => closed
* resolution: => wontfix

Comment:

I agree with Claude. Marking of adding a custom aggregate function as
`wontfix`.

--
Ticket URL: <https://code.djangoproject.com/ticket/34078#comment:3>