From 1228660d1a745bacbec00a714e6d434076f10852 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Mon, 17 Oct 2022 15:21:29 -0400 Subject: [PATCH] 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 --- doc/src/sgml/func.sgml | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 8c4eef9c44..a1aae10793 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -11403,6 +11403,12 @@ table2-mapping jsonb, but not for json. They follow the ordering rules for B-tree operations outlined at . + See also for the aggregate + function json_agg which aggregates record + values as JSON, the aggregate function + json_object_agg which aggregates pairs of values + into a JSON object, and their jsonb equivalents, + jsonb_agg and jsonb_object_agg. Some further operators also exist only for jsonb, as shown @@ -12233,15 +12239,6 @@ table2-mapping - - See also for the aggregate - function json_agg which aggregates record - values as JSON, and the aggregate function - json_object_agg which aggregates pairs of values - into a JSON object, and their jsonb equivalents, - jsonb_agg and jsonb_object_agg. - -