Обсуждение: List of pages from versions 9, 10, and 11 that don't exist in "current"

Hi there,

Does anyone have an easy way of seeing which pages from the 9.x, 10,
or 11 docs don't have a "current" version?

For example: https://www.postgresql.org/docs/11/recovery-config.html

Apologies in advance if there is a better list to email about this, let me know.

More context below, in case helpful.

Cheers,
Michael


For context, I've built a Firefox extension that redirects old
versions of the docs to their "current" version, except when either:
* you're already on the docs, or
* when a "current" version of the page doesn't exist.

Pages from older versions like 7.x and 8.x seem to be less of an issue
on search engines, so I'm thinking of supporting 9.0+ to reduce the
number of deprecated pages (wishful thinking perhaps?). Any advice
would be very welcome.

A response along the lines of "There are a LOT of these, please find
another way." would also be incredibly welcome.

I'm aware of some discussions in the past on ways to get search
engines to rank the "current" version of a page higher. It sounded
like a tough problem, so while people work out how to solve the root
issue(s), I thought a browser extension might help a little.

Code so far (MIT):
https://github.com/mchristofides/pg_docs_bot/

Extension link (v0.7, would like v1 to have this feature):
https://addons.mozilla.org/en-US/firefox/addon/pg_docs_bot/

On 4/25/20 1:12 PM, Michael Christofides wrote:
> Hi there,
>
> Does anyone have an easy way of seeing which pages from the 9.x, 10,
> or 11 docs don't have a "current" version?

I don't have an easy way, but I have a pedantic way:

1. Set up the pgweb app[1]
2. Set up the requirements for the docload.py utility
(tools/docs/docload.py)
3. Download the release source PG12 all the way down. You would really
only need one, likely the latest (e.g. at the time of this writing 12.2,
11.7, ...)
4. Load each one into the database. You may need to explicitly create
the "Version" objects in the admin for pgweb
5. Write SQL to see which filenames are present in an earlier version
but not a later one.

> For context, I've built a Firefox extension that redirects old
> versions of the docs to their "current" version, except when either:
> * you're already on the docs, or
> * when a "current" version of the page doesn't exist.

Sounds interesting. There is presently a patch[3] that could/should help
to address this case. The challenge, outside of the file that was the
impetus for the patch, would be finding the forwarding addresses for the
new pages. I believe Step 5 in the above would help with that.

Thanks!

Jonathan

[1] https://www.postgresql.org/developer/related-projects/
[2] https://www.postgresql.org/ftp/source/
[3]
https://www.postgresql.org/message-id/4490e710-85f7-87a9-74dd-793d27440bed%40postgresql.org

Thank you Jonathan.

Yes good thinking on a thorough way, I may need to go down that route.
I hadn't considered entries that exist in new versions but have
changed name or URL, glad to hear these might be handled well on the
docs themselves soon. I'll consider how to avoid getting in the way
there.

As a starting point, I remembered that depesz's site has the ability
to search release notes between versions. A search for deprecated
found me a few more:
https://why-upgrade.depesz.com/show?from=9.0&to=12.2&keywords=deprecated

Thanks again.

On Sat, Apr 25, 2020 at 6:26 PM Jonathan S. Katz <jkatz@postgresql.org> wrote:
>
> On 4/25/20 1:12 PM, Michael Christofides wrote:
> > Hi there,
> >
> > Does anyone have an easy way of seeing which pages from the 9.x, 10,
> > or 11 docs don't have a "current" version?
>
> I don't have an easy way, but I have a pedantic way:
>
> 1. Set up the pgweb app[1]
> 2. Set up the requirements for the docload.py utility
> (tools/docs/docload.py)
> 3. Download the release source PG12 all the way down. You would really
> only need one, likely the latest (e.g. at the time of this writing 12.2,
> 11.7, ...)
> 4. Load each one into the database. You may need to explicitly create
> the "Version" objects in the admin for pgweb
> 5. Write SQL to see which filenames are present in an earlier version
> but not a later one.
>
> > For context, I've built a Firefox extension that redirects old
> > versions of the docs to their "current" version, except when either:
> > * you're already on the docs, or
> > * when a "current" version of the page doesn't exist.
>
> Sounds interesting. There is presently a patch[3] that could/should help
> to address this case. The challenge, outside of the file that was the
> impetus for the patch, would be finding the forwarding addresses for the
> new pages. I believe Step 5 in the above would help with that.
>
> Thanks!
>
> Jonathan
>
> [1] https://www.postgresql.org/developer/related-projects/
> [2] https://www.postgresql.org/ftp/source/
> [3]
> https://www.postgresql.org/message-id/4490e710-85f7-87a9-74dd-793d27440bed%40postgresql.org
>