diff options
| author | Andrew Dunstan <andrew@dunslane.net> | 2025-01-03 09:23:46 -0500 |
|---|---|---|
| committer | Andrew Dunstan <andrew@dunslane.net> | 2025-01-03 10:36:30 -0500 |
| commit | 30f017626308a06cf0c0c82a706a1ba1b07df34a (patch) | |
| tree | bab5af8cca336d73ead7f8490fb6f58205646273 /doc/src | |
| parent | e28033fe1af8037e0fec8bb3a32fabbe18ac06b1 (diff) | |
| download | postgresql-30f017626308a06cf0c0c82a706a1ba1b07df34a.tar.gz postgresql-30f017626308a06cf0c0c82a706a1ba1b07df34a.zip | |
Document strange jsonb sort order for empty top level arrays
Slightly faulty logic in the original jsonb code (commit d9134d0a355)
results in an empty top level array sorting less than a json null. We
can't change the sort order now since it would affect btree indexes over
jsonb, so document the anomaly.
Backpatch to all live branches (13 .. 17)
In master, also add a code comment noting the anomaly.
Reported-by: Yan Chengpen
Reviewed-by: Jian He
Discussion: https://postgr.es/m/OSBPR01MB45199DD8DA2D1CECD50518188E272@OSBPR01MB4519.jpnprd01.prod.outlook.com
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/json.sgml | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/json.sgml b/doc/src/sgml/json.sgml index 54648c459c1..206eadb8f7b 100644 --- a/doc/src/sgml/json.sgml +++ b/doc/src/sgml/json.sgml @@ -584,12 +584,13 @@ SELECT jdoc->'guid', jdoc->'name' FROM api WHERE jdoc @@ '$.tags[*] == "qui"'; The <literal>btree</literal> ordering for <type>jsonb</type> datums is seldom of great interest, but for completeness it is: <synopsis> -<replaceable>Object</replaceable> > <replaceable>Array</replaceable> > <replaceable>Boolean</replaceable> > <replaceable>Number</replaceable> > <replaceable>String</replaceable> > <replaceable>Null</replaceable> +<replaceable>Object</replaceable> > <replaceable>Array</replaceable> > <replaceable>Boolean</replaceable> > <replaceable>Number</replaceable> > <replaceable>String</replaceable> > <replaceable>null</replaceable> <replaceable>Object with n pairs</replaceable> > <replaceable>object with n - 1 pairs</replaceable> <replaceable>Array with n elements</replaceable> > <replaceable>array with n - 1 elements</replaceable> </synopsis> + with the exception that (for historical reasons) an empty top level array sorts less than <replaceable>null</replaceable>. Objects with equal numbers of pairs are compared in the order: <synopsis> <replaceable>key-1</replaceable>, <replaceable>value-1</replaceable>, <replaceable>key-2</replaceable> ... |