From: Bruce Momjian <bruce@momjian.us>
Date: Mon, 17 Oct 2022 19:21:29 +0000 (-0400)
Subject: doc:  move the mention of aggregate JSON functions up in section
X-Git-Tag: REL_11_18~15
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=1228660d1a745bacbec00a714e6d434076f10852;p=thirdparty%2Fpostgresql.git

doc:  move the mention of aggregate JSON functions up in section

It was previously easily overlooked at the end of several tables.

Reported-by: Alex Denman

Discussion: https://postgr.es/m/166335888474.659.16897487975376230364@wrigleys.postgresql.org

Backpatch-through: 10
---

diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 8c4eef9c447..a1aae107932 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -11403,6 +11403,12 @@ table2-mapping
    <type>jsonb</type>, but not for <type>json</type>. They follow the
    ordering rules for B-tree operations outlined at <xref
    linkend="json-indexing"/>.
+   See also <xref linkend="functions-aggregate"/> for the aggregate
+   function <function>json_agg</function> which aggregates record
+   values as JSON, the aggregate function
+   <function>json_object_agg</function> which aggregates pairs of values
+   into a JSON object, and their <type>jsonb</type> equivalents,
+   <function>jsonb_agg</function> and <function>jsonb_object_agg</function>.
   </para>
   <para>
    Some further operators also exist only for <type>jsonb</type>, as shown
@@ -12233,15 +12239,6 @@ table2-mapping
     </para>
   </note>
 
-  <para>
-    See also <xref linkend="functions-aggregate"/> for the aggregate
-    function <function>json_agg</function> which aggregates record
-    values as JSON, and the aggregate function
-    <function>json_object_agg</function> which aggregates pairs of values
-    into a JSON object, and their <type>jsonb</type> equivalents,
-    <function>jsonb_agg</function> and <function>jsonb_object_agg</function>.
-  </para>
-
  </sect1>
 
  <sect1 id="functions-sequence">