On Tue, Jan 10, 2023 at 12:17 PM Dean Rasheed <dean.a.rasheed@gmail.com> wrote:
>
> On Tue, 10 Jan 2023 at 15:07, Magnus Hagander <magnus@hagander.net> wrote:
> >
> > The page simply doesn't exist, because the information is sperad out across multiple places. There is indeed a bug
inthat a link is generated to /current/ even if that page does not exist. But the information that's on there is also
wildlyout of date. This page was removed from the documentation in 2001, over 20 years ago. Linking to such obsolete
pagesin an article from 2023 doesn't exactly inspire confidence.
> >
>
> A Google search for "postgresql security" returns that page as the top
> non-featured result.
>
> Looking at the source of that page, it has <meta name="robots"
> content="nofollow" />. Changing that to "noindex" might help.
https://www.google.com/search?q=postgresql+security+hardening+guide
returns one result hosted on the PostgreSQL webserver. It is the old
article that has been condemned by the community.
Jeff
