Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tqNBp-003oqP-27 for pgsql-docs@arkaria.postgresql.org; Fri, 07 Mar 2025 02:11:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tqNBn-000QIT-Jo for pgsql-docs@arkaria.postgresql.org; Fri, 07 Mar 2025 02:11:51 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tqNBn-000QIL-Bn for pgsql-docs@lists.postgresql.org; Fri, 07 Mar 2025 02:11:51 +0000 Received: from mout-u-204.mailbox.org ([80.241.59.204]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tqNBi-001Pwa-2g for pgsql-docs@lists.postgresql.org; Fri, 07 Mar 2025 02:11:50 +0000 Received: from smtp1.mailbox.org (smtp1.mailbox.org [IPv6:2001:67c:2050:b231:465::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-u-204.mailbox.org (Postfix) with ESMTPS id 4Z88t76nRKz9spK; Fri, 7 Mar 2025 03:11:43 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ewie.name; s=MBO0001; t=1741313504; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=7xfZU7JV89Fn/OMDFQgdvyG8HFaqmYPjXCOyd0/Z9lQ=; b=0oJ76aC7x2wO87cM12pvtThhJY5UWKCd8H7Vyv6FN6wRUMrOALAkXPbZ5IaRH15/EztnPn ELYocfEvFLas0p4wldrV8c8GpNGACba+M2D3DqKEYIUtHUBikKuQ9/+l7JJc+doDOkeuYZ lNLYOAlzE77UBaEfpgKYWZpVKQ9eneYsv5RllGFrReqkJfSn4zrcCgbx5LEy7wpRIh72P1 0DLES1p5ayjeDvW4KopXVPB2AFbJA4s+s3AiyEt/rEq5fglCkvaEzVcb/Jc9Kjs0bqhPIb f0Xb8zIbFsYRLCuR75C6NuDC4v1OLYdUMI1DKmF6fGMzxt0bwEGF/dIbdXZHAg== Date: Fri, 7 Mar 2025 03:12:17 +0100 From: Erik Wienhold To: Jai Sharma Cc: pgsql-docs@lists.postgresql.org Subject: Re: Docs search does not work for the "@>" operator Message-ID: References: <875af479-d548-456d-bc6c-e196e76a5407@app.fastmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <875af479-d548-456d-bc6c-e196e76a5407@app.fastmail.com> X-Rspamd-Queue-Id: 4Z88t76nRKz9spK List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2025-03-03 19:35 +0100, Jai Sharma wrote: > When searching on the Postgres docs website, searching with the strings > `@>` or `"@>"` returns no results. > > Ordinarily, I would expect to see results returned including this page (which > was the page I was looking for): > https://www.postgresql.org/docs/17/functions-range.html Any operator, in fact, because pgweb implements its search with plainto_tsquery [1] which ignores punctuation. > Can the search be updated to work with these characters please? I don't see how because information about these operators (or any other punctuation) is lost when pages are converted to tsvector by the web crawler. Maybe a separate operator index where you could search with ctrl+f is an option. But I don't know if that is feasible with the current document structure without having to maintain basically two separate operator docs. But DocBook can certainly index symbols [2]. [1] https://git.postgresql.org/gitweb/?p=pgweb.git;a=blob;f=tools/search/sql/functions.sql;h=9ee5c4a51c0fba97e7e851a78db33669ecfc440e;hb=HEAD#l12 [2] https://www.postgresql.org/docs/current/bookindex.html#indexdiv-Symbols -- Erik Wienhold