From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Fetter <david@fetter.org>
Cc: Paul A Jungwirth <pj@illuminatedcomputing.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Jeff Davis <pgsql@j-davis.com>
Cc: Pgsql Hackers <pgsql-hackers@postgresql.org>
Subject: Re: range_agg
Date: Sat, 07 Mar 2020 18:45:44 -0500
Message-ID: <9016.1583624744@sss.pgh.pa.us> (raw)
In-Reply-To: <20200307221312.GV13804@fetter.org>
References: <20200304022849.GA5402@alvherre.pgsql>
<13800.1583612399@sss.pgh.pa.us>
<15764.1583615192@sss.pgh.pa.us>
<20200307221312.GV13804@fetter.org>
David Fetter <david@fetter.org> writes:
> There's another use case not yet covered here that could make this
> even more complex, we should probably plan for it: multi-ranges with
> weights.
I'm inclined to reject that as completely out of scope. The core
argument for unifying multiranges with ranges, if you ask me, is
to make the data type closed under union. Weights are from some
other universe.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, david@fetter.org, pj@illuminatedcomputing.com, alvherre@2ndquadrant.com, pavel.stehule@gmail.com, pgsql@j-davis.com
Subject: Re: range_agg
In-Reply-To: <9016.1583624744@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox