Thread: Versioned documentation search no longer working
Hello pg webmasters,
I've noticed that the documentation search on the site is currently in a poor state.
Previously, when looking at the documentation for a specific version (like https://web.archive.org/web/20170905162419/https://www.postgresql.org/docs/9.5/static/index.html ), searching for terms in the search box would take you to a filtered view for that version (with a "u" search parameter set to "/docs/$VERSION/", with version values like "9.5", "11", "current", and "dev" supported. This no longer works at all, and the experience of searching the documentation right now is consequently very poor.
Going to these URLs directly (as I do with a chrome custom search rule) will still work for most versions, but not for "current" or "11" (example: https://www.postgresql.org/search/?u=%2Fdocs%2Fcurrent%2F&q=array_agg ). In fact, no results of any kind seem to appear for version 11 (example: https://www.postgresql.org/search/?q=array_agg ).
Both of these issues (searches no longer automatically filter for the currently viewed version, and current documentation is not indexed) are serious regressions in the usability of the site.
Thanks for your work
Regards
Hi Kent, On 10/24/18 8:15 PM, Kent Ross wrote: > Previously, when looking at the documentation for a specific version You are correct, that was a regression. I have pushed up a fix for this. I apologize for the inconvenience. > > Going to these URLs directly (as I do with a chrome custom search rule) > will still work for most versions, but not for "current" or "11" Hm, this probably needs a script on the backend to be kicked off to index that. CCing Magnus who may know. There may be a delay due to him running a conference going on right now, but hopefully we can have this resolved ASAP. Thanks for reporting! Jonathan
Attachment
n Wed, Oct 24, 2018 at 11:49 PM Jonathan S. Katz <jkatz@postgresql.org> wrote:
Hi Kent,
On 10/24/18 8:15 PM, Kent Ross wrote:
> Previously, when looking at the documentation for a specific version
You are correct, that was a regression. I have pushed up a fix for this.
I apologize for the inconvenience.
>
> Going to these URLs directly (as I do with a chrome custom search rule)
> will still work for most versions, but not for "current" or "11"
Hm, this probably needs a script on the backend to be kicked off to
index that. CCing Magnus who may know. There may be a delay due to him
running a conference going on right now, but hopefully we can have this
resolved ASAP.
Of all things, this turns out to have been a firewall problem after a datacenter migration. The problem should now be fixed, and search work again properly.