Doc: shorten JSON_SERIALIZE example to avoid a PDF build warning.

There's no particular reason why this example has to use a
3-element array rather than 2-element.  Shortening it makes
the result bytea narrow enough to not cause a margin overrun
in A4 format.

diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 5047e090db02628e68a732a6b2f058608458a159..2ecf0482d8405a6053a1d450c3298a84e52f3d50 100644 (file)
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -19881,12 +19881,11 @@ SELECT JSON_SERIALIZE(JSON_SCALAR('foo'));
  "foo"
 (1 row)
 
-SELECT JSON_SERIALIZE('{"foo": "bar", "baz": [1, 2, 3]}' RETURNING bytea);
-                           json_serialize                           
---------------------------------------------------------------------
- \x7b22666f6f223a2022626172222c202262617a223a205b312c20322c20335d7d
+SELECT JSON_SERIALIZE('{"foo": "bar", "baz": [1, 2]}' RETURNING bytea);
+                        json_serialize
+--------------------------------------------------------------
+ \x7b22666f6f223a2022626172222c202262617a223a205b312c20325d7d
 (1 row)
-
 </screen>
     </sect5>
    </sect4>