agora inbox for pgsql-docs@postgresql.org
help / color / mirror / Atom feedOnline Documentation Search Issue
5+ messages / 5 participants
[nested] [flat]
* Online Documentation Search Issue
@ 2021-05-17 15:43 PG Doc comments form <noreply@postgresql.org>
0 siblings, 1 reply; 5+ messages in thread
From: PG Doc comments form @ 2021-05-17 15:43 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org; +Cc: mike@vasto.la
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/functions-comparison.html
Description:
Hi,
Just an FYI, but I'm running into a somewhat annoying issue with the
documentation search that I'm not sure you're aware of.
Namely, searching for "BETWEEN" (upper or lowercase) yields zero results.
Trying a few different search queries right now, it appears I might be just
running into an issue where my query is a stopword, but in this case it's
particularly frustrating because (even once I realize that) there is no
obvious alternative search query. (I wouldn't have thought to search for
"Comparison Functions", the page where it's actually explained.)
Is there any way your search platform can be set to index all text that
appears in the documentation inside 'code' tags? Or could some sort of
suggestion bar be added to the results page so that if a query contains a
keyword (especially if it consists entirely of the keyword), a link is
presented to go to it's page?
Barring that, could searching a stopword trigger a message (and perhaps a
link to search it on Google) other than just "no results found"?
Thanks,
Mike
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Online Documentation Search Issue
@ 2021-05-17 16:14 Karoline Pauls <contact@karolinepauls.com>
parent: PG Doc comments form <noreply@postgresql.org>
0 siblings, 1 reply; 5+ messages in thread
From: Karoline Pauls @ 2021-05-17 16:14 UTC (permalink / raw)
To: mike@vasto.la; pgsql-docs@lists.postgresql.org
HAVING is another stop-word.
-------- Original Message --------
On 17 May 2021, 16:43, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/13/functions-comparison.html
> Description:
>
> Hi,
> Just an FYI, but I'm running into a somewhat annoying issue with the
> documentation search that I'm not sure you're aware of.
> Namely, searching for "BETWEEN" (upper or lowercase) yields zero results.
>
> Trying a few different search queries right now, it appears I might be just
> running into an issue where my query is a stopword, but in this case it's
> particularly frustrating because (even once I realize that) there is no
> obvious alternative search query. (I wouldn't have thought to search for
> "Comparison Functions", the page where it's actually explained.)
>
> Is there any way your search platform can be set to index all text that
> appears in the documentation inside 'code' tags? Or could some sort of
> suggestion bar be added to the results page so that if a query contains a
> keyword (especially if it consists entirely of the keyword), a link is
> presented to go to it's page?
>
> Barring that, could searching a stopword trigger a message (and perhaps a
> link to search it on Google) other than just "no results found"?
>
> Thanks,
> Mike
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Online Documentation Search Issue
@ 2021-05-18 06:56 Laurenz Albe <laurenz.albe@cybertec.at>
parent: Karoline Pauls <contact@karolinepauls.com>
0 siblings, 0 replies; 5+ messages in thread
From: Laurenz Albe @ 2021-05-18 06:56 UTC (permalink / raw)
To: Karoline Pauls <contact@karolinepauls.com>; mike@vasto.la; pgsql-docs@lists.postgresql.org
On Mon, 2021-05-17 at 16:14 +0000, Karoline Pauls wrote:
>
> On 17 May 2021, 16:43, PG Doc comments form < noreply@postgresql.org> wrote:
> > Just an FYI, but I'm running into a somewhat annoying issue with the
> > documentation search that I'm not sure you're aware of.
> > Namely, searching for "BETWEEN" (upper or lowercase) yields zero results.
> >
> > Trying a few different search queries right now, it appears I might be just
> > running into an issue where my query is a stopword, but in this case it's
> > particularly frustrating because (even once I realize that) there is no
> > obvious alternative search query. (I wouldn't have thought to search for
> > "Comparison Functions", the page where it's actually explained.)
> >
> > Is there any way your search platform can be set to index all text that
> > appears in the documentation inside 'code' tags? Or could some sort of
> > suggestion bar be added to the results page so that if a query contains a
> > keyword (especially if it consists entirely of the keyword), a link is
> > presented to go to it's page?
> >
> > Barring that, could searching a stopword trigger a message (and perhaps a
> > link to search it on Google) other than just "no results found"?
>
> HAVING is another stop-word.
I find 518 lines with "between" in the documentation, so I am not sure if
removing that stopword would be beneficial.
But there is an index for the documentation:
https://www.postgresql.org/docs/current/bookindex.html#indexdiv-B
"BETWEEN" is in the index.
So is "HAVING". Removing "HAVING" as a stopword would mean indexing
"have", and that is obviously not going to help anybody.
Yours,
Laurenz Albe
^ permalink raw reply [nested|flat] 5+ messages in thread
* Docs search does not work for the "@>" operator
@ 2025-03-03 18:35 Jai Sharma <jai@jai.moe>
0 siblings, 1 reply; 5+ messages in thread
From: Jai Sharma @ 2025-03-03 18:35 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org
Hello Postgres Docs,
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
Can the search be updated to work with these characters please?
Thanks,
Jai
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Docs search does not work for the "@>" operator
@ 2025-03-07 02:12 Erik Wienhold <ewie@ewie.name>
parent: Jai Sharma <jai@jai.moe>
0 siblings, 0 replies; 5+ messages in thread
From: Erik Wienhold @ 2025-03-07 02:12 UTC (permalink / raw)
To: Jai Sharma <jai@jai.moe>; +Cc: pgsql-docs@lists.postgresql.org
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=9ee5c4a51c0...
[2] https://www.postgresql.org/docs/current/bookindex.html#indexdiv-Symbols
--
Erik Wienhold
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2025-03-07 02:12 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2021-05-17 15:43 Online Documentation Search Issue PG Doc comments form <noreply@postgresql.org>
2021-05-17 16:14 ` Karoline Pauls <contact@karolinepauls.com>
2021-05-18 06:56 ` Laurenz Albe <laurenz.albe@cybertec.at>
2025-03-03 18:35 Docs search does not work for the "@>" operator Jai Sharma <jai@jai.moe>
2025-03-07 02:12 ` Re: Docs search does not work for the "@>" operator Erik Wienhold <ewie@ewie.name>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox