Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nZdIq-0002Qy-5y for pgsql-hackers@arkaria.postgresql.org; Wed, 30 Mar 2022 18:44:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nZdHr-0002ql-14 for pgsql-hackers@arkaria.postgresql.org; Wed, 30 Mar 2022 18:43:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nZdHq-0002qa-1v for pgsql-hackers@lists.postgresql.org; Wed, 30 Mar 2022 18:43:18 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nZdHh-0003zo-MP for pgsql-hackers@lists.postgresql.org; Wed, 30 Mar 2022 18:43:17 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 5B6CA5C01E3; Wed, 30 Mar 2022 14:43:06 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 30 Mar 2022 14:43:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=cFGyU9IfLeQ/j3PRHfxmqAYJVkKBhK6UQW4rKrDvl98=; b=RLQENopu 1hefA2iMH1mj1VbybOiS2SXjrJghT0FcILv9fZGGdbJBIZcQryj6OKUVz3+0ugAk UaaM3HqRMlZZN/Y0uDaSAMPT/7e50Q0X4tvE/sEmd+REv8Vz1Dqf2KWGXCmln8fs Tt/Q1ZJXSki1S4yo7UMtTnpBMphTc6uH3+tXoHxkGlvdIXtzw/fTXECF806sT3o4 ROvrt5RDJwYZNZd4wAHXROAE8PQkIB0MgwTssKaKz6atBihfec0vwwkcWD1bDGft Fpxb1wWLSUqF5itfxUGou4pscCJnqZN8b0iIO5zJrmXXuOyCrjBHuHujbWkeIcHg y+nexBH5KHnyDw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudeivddguddvkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeefjeegheetuefhveev udelueeftdejteeiffetvdduhfdtieefgfeutedtveeggfenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghu thesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 30 Mar 2022 14:43:04 -0400 (EDT) Message-ID: <4112581f-1d01-8a62-3030-22ca4fda2e63@enterprisedb.com> Date: Wed, 30 Mar 2022 20:43:03 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: range_agg with multirange inputs Content-Language: en-US To: Paul Jungwirth , Chapman Flack , pgsql-hackers@lists.postgresql.org References: <007ef255-35ef-fd26-679c-f97e7a7f30c2@illuminatedcomputing.com> <007ef255-35ef-fd26-679c-f97e7a7f30c2@illuminatedcomputing.com> <164592443404.882.11296254043197567171.pgcf@coridan.postgresql.org> <6556b959-f839-aee2-4b4b-0b5107c0db11@illuminatedcomputing.com> <621E912C.3020307@anastigmatix.net> <42454377-d914-0e22-37da-1b63ce3b9f9d@illuminatedcomputing.com> <622A7690.4020800@anastigmatix.net> <71eabe81-3e69-0476-347a-c8342de5cd41@illuminatedcomputing.com> From: Peter Eisentraut In-Reply-To: <71eabe81-3e69-0476-347a-c8342de5cd41@illuminatedcomputing.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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 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. I kept those messages as "range" or "multirange" separately, instead of "range or multirange". This way, we don't have to update all the messages of this kind when a new function is added. Since these are only internal messages anyway, I opted for higher maintainability.