Re: pg_replication_slots page links

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Şahap Aşçı <sahapasci(at)gmail(dot)com>, pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: pg_replication_slots page links
Date: 2017-11-10 14:50:52
Message-ID: 27003.1510325452@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Fri, Nov 10, 2017 at 3:41 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 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.

The db table doesn't result in generating redirects then, I take it?

Since you already have a fix, I suppose we should leave well enough
alone. This isn't a big enough deal to expend a lot of sweat on.

regards, tom lane

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Magnus Hagander 2017-11-10 14:55:29 Re: pg_replication_slots page links
Previous Message Magnus Hagander 2017-11-10 14:43:42 Re: pg_replication_slots page links