Re: "GIN and GiST Index Types" page is about usage in full text search, but looks general purpose
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Geoghegan <pg@bowt.ie>
Cc: piotrowski@prisma.io, Pg Docs <pgsql-docs@lists.postgresql.org>,
"Jonathan S. Katz" <jkatz@postgresql.org>
Date: 2022-04-12T20:28:47Z
Lists: pgsql-docs
Attachments
- doc-tweak-full-text-index-docs.patch (text/x-diff) patch
Peter Geoghegan <pg@bowt.ie> writes: > On Tue, Apr 12, 2022 at 12:49 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> I think we should take the index type names out of the section title >> entirely, and name it something generic like "Preferred Index Types for >> Full Text Search". > Agreed. Proposed patch attached. The existing text already says "GIN indexes are the preferred text search index type", so I'm not sure we need to go further than that about guiding people which one to use. In particular, since GIN can't support included columns, we can't really deprecate GiST altogether here. > There is always the extreme option of excluding older versions in > robots.txt. I bet that would work. Yeah, I was wondering about that too. It's sort of the nuclear option, but if we don't want to modify EOL'd versions then we may not have any other way to keep Google from glomming onto them. regards, tom lane
Commits
-
Doc: tweak textsearch.sgml for SEO purposes.
- 2e1f30270b04 10.21 landed
- d53f689f8f75 11.16 landed
- 2eb3ec8f4961 12.11 landed
- 71e0736b6577 13.7 landed
- 8320a34d38e2 14.3 landed
- aa36e7dd38d3 15.0 landed