doc: remove GIN vs. GiST performance mention
This is a followup to commit 6d8b2aa83a
.
This commit is contained in:
parent
69769a3a6e
commit
8e1ad1b37c
|
@ -277,9 +277,6 @@
|
||||||
<para>
|
<para>
|
||||||
The choice between GiST and GIN indexing depends on the relative
|
The choice between GiST and GIN indexing depends on the relative
|
||||||
performance characteristics of GiST and GIN, which are discussed elsewhere.
|
performance characteristics of GiST and GIN, which are discussed elsewhere.
|
||||||
As a rule of thumb, a GIN index is faster to search than a GiST index, but
|
|
||||||
slower to build or update; so GIN is better suited for static data and GiST
|
|
||||||
for often-updated data.
|
|
||||||
</para>
|
</para>
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
|
|
|
@ -355,9 +355,6 @@ SELECT * FROM test_trgm WHERE t ~ '(foo|bar)';
|
||||||
<para>
|
<para>
|
||||||
The choice between GiST and GIN indexing depends on the relative
|
The choice between GiST and GIN indexing depends on the relative
|
||||||
performance characteristics of GiST and GIN, which are discussed elsewhere.
|
performance characteristics of GiST and GIN, which are discussed elsewhere.
|
||||||
As a rule of thumb, a GIN index is faster to search than a GiST index, but
|
|
||||||
slower to build or update; so GIN is better suited for static data and GiST
|
|
||||||
for often-updated data.
|
|
||||||
</para>
|
</para>
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue