Skip to content

Commit 5a49558

Browse files
committed
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
1 parent 63a3709 commit 5a49558

File tree

1 file changed

+6
-9
lines changed

1 file changed

+6
-9
lines changed

doc/src/sgml/func.sgml

Lines changed: 6 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -11260,6 +11260,12 @@ table2-mapping
1126011260
<type>jsonb</type>, but not for <type>json</type>. They follow the
1126111261
ordering rules for B-tree operations outlined at <xref
1126211262
linkend="json-indexing">.
11263+
See also <xref linkend="functions-aggregate"> for the aggregate
11264+
function <function>json_agg</function> which aggregates record
11265+
values as JSON, the aggregate function
11266+
<function>json_object_agg</function> which aggregates pairs of values
11267+
into a JSON object, and their <type>jsonb</type> equivalents,
11268+
<function>jsonb_agg</function> and <function>jsonb_object_agg</function>.
1126311269
</para>
1126411270
<para>
1126511271
Some further operators also exist only for <type>jsonb</type>, as shown
@@ -12090,15 +12096,6 @@ table2-mapping
1209012096
</para>
1209112097
</note>
1209212098

12093-
<para>
12094-
See also <xref linkend="functions-aggregate"> for the aggregate
12095-
function <function>json_agg</function> which aggregates record
12096-
values as JSON, and the aggregate function
12097-
<function>json_object_agg</function> which aggregates pairs of values
12098-
into a JSON object, and their <type>jsonb</type> equivalents,
12099-
<function>jsonb_agg</> and <function>jsonb_object_agg</>.
12100-
</para>
12101-
1210212099
</sect1>
1210312100

1210412101
<sect1 id="functions-sequence">

0 commit comments

Comments
 (0)