From: Tom Lane <tgl@sss.pgh.pa.us>
To: Shay Rojansky <roji@roji.org>
cc: pgsql-docs@postgresql.org
Subject: Re: Incorrect and missing docs for range_intersect_agg
In-reply-to: 
 <CADT4RqAktzP7t6SFf0Xqm9YhahzvsmxFbzXe-gFOd=+_CHm0JA@mail.gmail.com>
References: 
 <CADT4RqAktzP7t6SFf0Xqm9YhahzvsmxFbzXe-gFOd=+_CHm0JA@mail.gmail.com>
Comments: In-reply-to Shay Rojansky <roji@roji.org>
	message dated "Fri, 27 May 2022 23:35:10 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3493920.1653844709.1@sss.pgh.pa.us>
Date: Sun, 29 May 2022 13:18:29 -0400
Message-ID: <3493921.1653844709@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3493921.1653844709%40sss.pgh.pa.us>
Precedence: bulk

Shay Rojansky <roji@roji.org> writes:
> range_intersect_agg is documented to return anymultirange (on this
> page[1]), but it actually returns a range.

The form with anyrange input, yeah.

> In addition, range_intersect_agg also accepts a multirange as its
> parameter, but that's not documented on the same page.

Hmm, this was fixed recently in HEAD, but it should have been
back-patched to v14 and was not.

Will fix, thanks for noticing!

			regards, tom lane