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 1nuhcI-00037S-Fn for pgsql-docs@arkaria.postgresql.org; Fri, 27 May 2022 21:35:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nuhcG-0000gW-Q2 for pgsql-docs@arkaria.postgresql.org; Fri, 27 May 2022 21:35:28 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nuhcG-0000gL-GT for pgsql-docs@lists.postgresql.org; Fri, 27 May 2022 21:35:28 +0000 Received: from mail-yb1-xb34.google.com ([2607:f8b0:4864:20::b34]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nuhc9-0000x3-LS for pgsql-docs@postgresql.org; Fri, 27 May 2022 21:35:27 +0000 Received: by mail-yb1-xb34.google.com with SMTP id s14so9899706ybc.10 for ; Fri, 27 May 2022 14:35:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=roji.org; s=roji; h=mime-version:from:date:message-id:subject:to; bh=ukcAaW2pCYTmJSnuA5KRvjY3l0qdrVQ22p98HcD+J+k=; b=hQffAOL1aORwil16PYL7HVbzuAqc+JSNxUAJOTeGBPOU0c0LlRkyhSJYGDucC3vRng XjPqqENU/AbtqIzFCApPmxZ+ZlGpP9nQ5GX5IHWSR8fXQ/ZQPQFQWunp2ZCxmxOT+86x hoh4HOpECIRiDrOPYvKTTL85s5bvLwC+YQDO8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=ukcAaW2pCYTmJSnuA5KRvjY3l0qdrVQ22p98HcD+J+k=; b=EVjHTsJ3hKQMY9056jGJJKwbiI/peF2SKCS6MpPb115HKAfSxrnM91O0xDZrVBHgKr QX5nfmSPsigwH3Wkn/p6umGG3QdLop3mgPCplPCmZUoD4H76UZHswRXrSDWzqHRvV3vK Aama99yjgl7k79Y99fg1s+IfIf+q17CbeqsV3VrVNxyt6tZk48qLnaOGQv6DI2POLnZe Ns61eyB303QREMmR3fOvusLkjvQ9wZY2hpVjUuc94K6XVu5m7jJWibwOZv6nwaiJZRRk Zdj+kjdUa92j54hHAKMk7v6MtecHgO3e9e2JsiS7ua5YqjFQVA4DG1fhLtIUSjtUJkn4 x4xA== X-Gm-Message-State: AOAM530Rn7Xmp76FDE9XJBEkKxgegisrnyiP1/n5RG1OMV8kEW0Q2g6s SwxwLnDvBjZ847M/u0wKH3ISCQnhQlmg/oBvTTqMiAsE/lTrSw== X-Google-Smtp-Source: ABdhPJzeYpzi+R/Uuhv2ce1o3XWzaCFIDWATlt2f2VGvCHSjWjJm8x+3gkwWiOlzkhy3hkLEGHSmthqZxIfDGz4kPRE= X-Received: by 2002:a5b:148:0:b0:650:15bd:97ab with SMTP id c8-20020a5b0148000000b0065015bd97abmr23091590ybp.231.1653687320890; Fri, 27 May 2022 14:35:20 -0700 (PDT) MIME-Version: 1.0 From: Shay Rojansky Date: Fri, 27 May 2022 23:35:10 +0200 Message-ID: Subject: Incorrect and missing docs for range_intersect_agg To: pgsql-docs@postgresql.org Content-Type: multipart/alternative; boundary="00000000000054e33b05e00515f5" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000054e33b05e00515f5 Content-Type: text/plain; charset="UTF-8" Hi all, range_intersect_agg is documented to return anymultirange (on this page[1]), but it actually returns a range. In addition, range_intersect_agg also accepts a multirange as its parameter, but that's not documented on the same page. Note that range_agg does *not* accept a multirange (possibly already added for PG15, see this[2]). Thanks, Shay [1] https://www.postgresql.org/docs/current/functions-aggregate.html [2] https://www.mail-archive.com/pgsql-hackers@lists.postgresql.org/msg105057.html --00000000000054e33b05e00515f5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

range_intersect_agg is document= ed to return anymultirange (on this page[1]), but it actually returns a ran= ge.

In addition, range_intersect_agg also accepts = a multirange as its parameter, but that's not documented on the same pa= ge. Note that range_agg does *not* accept a multirange (possibly already ad= ded for PG15, see this[2]).

Thanks,

=
Shay

--00000000000054e33b05e00515f5--