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 1neO9o-0005Ni-66 for pgsql-docs@arkaria.postgresql.org; Tue, 12 Apr 2022 21:34:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1neO9l-0002Ot-3Y for pgsql-docs@arkaria.postgresql.org; Tue, 12 Apr 2022 21:34:37 +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 1neO9k-0002O6-P6 for pgsql-docs@lists.postgresql.org; Tue, 12 Apr 2022 21:34:36 +0000 Received: from mail-ed1-x52a.google.com ([2a00:1450:4864:20::52a]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1neO9d-00012W-Sx for pgsql-docs@lists.postgresql.org; Tue, 12 Apr 2022 21:34:35 +0000 Received: by mail-ed1-x52a.google.com with SMTP id v15so59797edb.12 for ; Tue, 12 Apr 2022 14:34:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bowt-ie.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=23p8Y1Ei11Qn7j4kZ3fz1DCm4kQEW+jUoi7a3Eetcx4=; b=5FOTVDCHd4HLoZvK5fsv7QQTVRHfRZajiVv/ma3aP8d9yeRVU+bt9R02Cts/xdc9ZV pQrGtj33TTVnwznHNq46iXxDwnuJAqUZYpHgWjlUTVKhF6BzE+RqleKwn+5NFf/Ymfhu w1hU3I8EMqoi29rToUnAzdYccBFIL3+lD8GLyxuRAuuS8TxImiHDmRUomAxklQenrhsj 7tXRHvr/6fRG6Tm/vtqJ5IxmjzNhgBnL/hi5ylFB7s/w+k3qOXvnCH2KbeRvur0Fcrin ZmPCcNCLZfk0lsczhdi0OfrAJzTt/G9UzqYVMJD4lq/b25XYcd3A4PQH7v3F/QkhI+im VwwQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=23p8Y1Ei11Qn7j4kZ3fz1DCm4kQEW+jUoi7a3Eetcx4=; b=p18S0VTa3uwFeF34S+IW/KaAq+11qUldUazhQTNIc/6mjfPmyaRxKmqQlT6wJKBTge NG7wRRsPlo3buLHKAIuwY+/df1W+uRNKt8umudt0CHXBupS9ZJe623dmOYYlhK25kcBx gyRiMjzY25UsfyWyeWm5HR0Ml909/eplTUwAhQMnYZz6fT6zuo4nrsZSjVolg7JoHL6b LMccaBnaKywJEajiv0iCP+s+iSJsh2TMJO3l7uY3kbY2Ih8mdTWVvcmDuT0twFpZpVBe 6eqfaR8hFYVSRgjpyVRsMwhG8/oEP5FS0iOsXTRhGhpgO7YxJ8COn0jJDHlBmjEy9WnD fe3A== X-Gm-Message-State: AOAM5310D5ymOTII8XogSb/PpZINHPiydz63vNgfiVPAewTrshFu9YW6 5ACP+ffbzdtAlEiYhu5GAg+dirUxSGc6D1kmUcHgzQ== X-Google-Smtp-Source: ABdhPJwv4NqmTnuzBMqFAxpNjvo7UvWHdmDNvQRWEiSkXAEMS3FtQoO05XoryOQ/jK2uj40rZpCJfMKB6XbZZBllaJU= X-Received: by 2002:a05:6402:14b:b0:418:d06e:5d38 with SMTP id s11-20020a056402014b00b00418d06e5d38mr39615488edu.90.1649799267313; Tue, 12 Apr 2022 14:34:27 -0700 (PDT) MIME-Version: 1.0 References: <164978902252.1276550.9330175733459697101@wrigleys.postgresql.org> <911427.1649792973@sss.pgh.pa.us> <915352.1649795327@sss.pgh.pa.us> In-Reply-To: <915352.1649795327@sss.pgh.pa.us> From: Peter Geoghegan Date: Tue, 12 Apr 2022 14:34:01 -0700 Message-ID: Subject: Re: "GIN and GiST Index Types" page is about usage in full text search, but looks general purpose To: Tom Lane Cc: piotrowski@prisma.io, Pg Docs , "Jonathan S. Katz" Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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. > > 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. I think that our recent decision to just live with the downsides that go with making the most recent stable release docs canonical was a wise one, on balance. The reality is that we have very few ways of influencing search results from Google. 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. -- Peter Geoghegan