Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1neOuZ-0000bJ-IA for pgsql-docs@arkaria.postgresql.org; Tue, 12 Apr 2022 22:22:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1neOuY-0000zk-FS for pgsql-docs@arkaria.postgresql.org; Tue, 12 Apr 2022 22:22:58 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1neOuY-0000zP-8C for pgsql-docs@lists.postgresql.org; Tue, 12 Apr 2022 22:22:58 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1neOuW-0001Xz-5c; Tue, 12 Apr 2022 22:22:57 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 23CMMrtI1008197; Tue, 12 Apr 2022 18:22:53 -0400 From: Tom Lane To: Peter Geoghegan cc: piotrowski@prisma.io, Pg Docs , "Jonathan S. Katz" Subject: Re: "GIN and GiST Index Types" page is about usage in full text search, but looks general purpose In-reply-to: References: <164978902252.1276550.9330175733459697101@wrigleys.postgresql.org> <911427.1649792973@sss.pgh.pa.us> <915352.1649795327@sss.pgh.pa.us> Comments: In-reply-to Peter Geoghegan message dated "Tue, 12 Apr 2022 14:34:01 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1008195.1649802173.1@sss.pgh.pa.us> Date: Tue, 12 Apr 2022 18:22:53 -0400 Message-ID: <1008196.1649802173@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Peter Geoghegan writes: > On Tue, Apr 12, 2022 at 1:28 PM Tom Lane wrote: >> 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. > LGTM. Done that way, then. > I don't know enough about the topic to be able to claim that the > robots.txt solution would also work out well, in about the same way. > But I suspect that it might, and know that it's a reversible process. Yeah, it's outside my expertise too. regards, tom lane