Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1jAj8m-0007Sd-8n for pgsql-hackers@arkaria.postgresql.org; Sat, 07 Mar 2020 23:45:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jAj8l-0005qU-2p for pgsql-hackers@arkaria.postgresql.org; Sat, 07 Mar 2020 23:45:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1jAj8k-0005qL-QO for pgsql-hackers@lists.postgresql.org; Sat, 07 Mar 2020 23:45:54 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jAj8i-0002b4-Jw for pgsql-hackers@postgresql.org; Sat, 07 Mar 2020 23:45:54 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 027NjiDP009017; Sat, 7 Mar 2020 18:45:44 -0500 From: Tom Lane To: David Fetter cc: Paul A Jungwirth , Alvaro Herrera , Pavel Stehule , Jeff Davis , Pgsql Hackers Subject: Re: range_agg 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> Comments: In-reply-to David Fetter message dated "Sat, 07 Mar 2020 23:13:13 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9015.1583624744.1@sss.pgh.pa.us> Date: Sat, 07 Mar 2020 18:45:44 -0500 Message-ID: <9016.1583624744@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk David Fetter 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