postgres.git / summary / log / commit / refs
commit a2586dece1953e7c395b533bf52b54b5e7bb3a3c
Author: Bruce Momjian <bruce@momjian.us>
Date: Sat Jun 21 19:33:22 2014 +0000
First released in: 9.5.0, 9.4.0
doc: adjust JSONB GIN index description
Backpatch through 9.4
doc/src/sgml/json.sgml | 15 ++++++++++-----
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/json.sgml b/doc/src/sgml/json.sgml
index 66426189ca5..d55a08fb18a 100644
--- a/doc/src/sgml/json.sgml
+++ b/doc/src/sgml/json.sgml
@@ -460,11 +460,16 @@ SELECT jdoc->'guid', jdoc->'name' FROM api WHERE jdoc @> '{"tags": ["qu
and a <literal>jsonb_path_ops</literal> GIN index is that the former
creates independent index items for each key and value in the data,
while the latter creates index items only for each value in the
- data.<footnote><para>For this purpose, the term <quote>value</>
- includes array elements, though JSON terminology sometimes considers
- array elements distinct from values within objects.</para></footnote>
- But in <literal>jsonb_path_ops</literal>, each index item is a hash
- of both the value and the key(s) leading to it; for example to index
+ data.
+ <footnote>
+ <para>
+ For this purpose, the term <quote>value</> includes array elements,
+ though JSON terminology sometimes considers array elements distinct
+ from values within objects.
+ </para>
+ </footnote>
+ Basically, each <literal>jsonb_path_ops</literal> index item is
+ a hash of the value and the key(s) leading to it; for example to index
<literal>{"foo": {"bar": "baz"}}</literal>, a single index item would
be created incorporating all three of <literal>foo</>, <literal>bar</>,
and <literal>baz</> into the hash value. Thus a containment query
[parent: 750c0351ea9c]