From 8e1ad1b37c7afdf99815f9ed1ca255264e0b3f9e Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 28 Jun 2016 16:00:40 -0400 Subject: [PATCH] doc: remove GIN vs. GiST performance mention This is a followup to commit 6d8b2aa83af70e20323caf23961667dc4c149276. --- doc/src/sgml/intarray.sgml | 3 --- doc/src/sgml/pgtrgm.sgml | 3 --- 2 files changed, 6 deletions(-) diff --git a/doc/src/sgml/intarray.sgml b/doc/src/sgml/intarray.sgml index aae6022c33..ccb1fdecea 100644 --- a/doc/src/sgml/intarray.sgml +++ b/doc/src/sgml/intarray.sgml @@ -277,9 +277,6 @@ The choice between GiST and GIN indexing depends on the relative 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. diff --git a/doc/src/sgml/pgtrgm.sgml b/doc/src/sgml/pgtrgm.sgml index ef3c15d705..e0d98f6dd8 100644 --- a/doc/src/sgml/pgtrgm.sgml +++ b/doc/src/sgml/pgtrgm.sgml @@ -355,9 +355,6 @@ SELECT * FROM test_trgm WHERE t ~ '(foo|bar)'; The choice between GiST and GIN indexing depends on the relative 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.