Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 884dede

Browse files
committed
doc: adjust JSONB GIN index description
Backpatch through 9.4
1 parent a52f2a0 commit 884dede

File tree

1 file changed

+10
-5
lines changed

1 file changed

+10
-5
lines changed

doc/src/sgml/json.sgml

+10-5
Original file line numberDiff line numberDiff line change
@@ -460,11 +460,16 @@ SELECT jdoc->'guid', jdoc->'name' FROM api WHERE jdoc @> '{"tags": ["qu
460460
and a <literal>jsonb_path_ops</literal> GIN index is that the former
461461
creates independent index items for each key and value in the data,
462462
while the latter creates index items only for each value in the
463-
data.<footnote><para>For this purpose, the term <quote>value</>
464-
includes array elements, though JSON terminology sometimes considers
465-
array elements distinct from values within objects.</para></footnote>
466-
But in <literal>jsonb_path_ops</literal>, each index item is a hash
467-
of both the value and the key(s) leading to it; for example to index
463+
data.
464+
<footnote>
465+
<para>
466+
For this purpose, the term <quote>value</> includes array elements,
467+
though JSON terminology sometimes considers array elements distinct
468+
from values within objects.
469+
</para>
470+
</footnote>
471+
Basically, each <literal>jsonb_path_ops</literal> index item is
472+
a hash of the value and the key(s) leading to it; for example to index
468473
<literal>{"foo": {"bar": "baz"}}</literal>, a single index item would
469474
be created incorporating all three of <literal>foo</>, <literal>bar</>,
470475
and <literal>baz</> into the hash value. Thus a containment query

0 commit comments

Comments
 (0)