Re: [DOCS] pg_replication_slots page links - Mailing list pgsql-docs

From Magnus Hagander
Subject Re: [DOCS] pg_replication_slots page links
Date
Msg-id CABUevEy1uf856oVAXtr0VcQYBm7wPgFi_axO4-_CsJHkSCYDVw@mail.gmail.com
Whole thread Raw
In response to Re: [DOCS] pg_replication_slots page links  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [DOCS] pg_replication_slots page links  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-docs
On Fri, Nov 10, 2017 at 3:41 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Magnus Hagander <magnus@hagander.net> writes:
> On Fri, Nov 10, 2017 at 6:58 AM, Alvaro Herrera <alvherre@alvh.no-ip.org>
> wrote:
>>> Because the name of the page has changed.  Not much to do about that at
>>> this point.

> Is this going to affect a single page, pg_replication_slots,  or is this a
> systematic change that's going to be hitting a whole class of pages?

I think this can be blamed on a9ba6195f, which I only back-patched as
far as 9.5 --- guess I didn't realize that the bogus section name
existed further back.  So I think the answer to your direct question
is "a single page", but maybe we should instead proceed by bringing 9.4
into line with the later branches and then updating the docs?

Adding the mapping to the website was a single row in a db table, and is already done, so it wasn't a lot of work. But there might be other reasons to change it of course, for consistency.

Of course, actually *changing* it in 9.4 now will break any external links pointing to it. Links within our own documentation will pick it up and change accordingly, but anything that's linking from the outside will generate 404s. 

--

pgsql-docs by date:

Previous
From: Tom Lane
Date:
Subject: Re: [DOCS] pg_replication_slots page links
Next
From: Tom Lane
Date:
Subject: Re: [DOCS] pg_replication_slots page links