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.
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 >