Commit8e1ad1b

committed

doc: remove GIN vs. GiST performance mention

This is a followup to commit6d8b2aa.

1 parent69769a3 commit8e1ad1bCopy full SHA for 8e1ad1b

File tree

-6

lines changed

-6

lines changed

Lines changed: 0 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -277,9 +277,6 @@`
`277`	`277`	`<para>`
`278`	`278`	`The choice between GiST and GIN indexing depends on the relative`
`279`	`279`	`performance characteristics of GiST and GIN, which are discussed elsewhere.`
`280`		`- As a rule of thumb, a GIN index is faster to search than a GiST index, but`
`281`		`- slower to build or update; so GIN is better suited for static data and GiST`
`282`		`- for often-updated data.`
`283`	`280`	`</para>`
`284`	`281`	`</sect2>`
`285`	`282`

Lines changed: 0 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -355,9 +355,6 @@ SELECT * FROM test_trgm WHERE t ~ '(foo\|bar)';`
`355`	`355`	`<para>`
`356`	`356`	`The choice between GiST and GIN indexing depends on the relative`
`357`	`357`	`performance characteristics of GiST and GIN, which are discussed elsewhere.`
`358`		`- As a rule of thumb, a GIN index is faster to search than a GiST index, but`
`359`		`- slower to build or update; so GIN is better suited for static data and GiST`
`360`		`- for often-updated data.`
`361`	`358`	`</para>`
`362`	`359`	`</sect2>`
`363`	`360`

Comments

(0)