Re: Add docs stub for recovery.conf

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Craig Ringer <craig.ringer@enterprisedb.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-11-11T20:01:55Z
Lists: pgsql-hackers
On Wed, Nov 11, 2020 at 08:59:40PM +0100, Daniel Gustafsson wrote:
> > On 11 Nov 2020, at 20:44, Bruce Momjian <bruce@momjian.us> wrote:
> > On Tue, Nov 10, 2020 at 01:38:14PM +0800, Craig Ringer wrote:
> 
> >> I noticed that when recovery.conf was removed in 2dedf4d9a8 (yay!) the docs for
> >> it were removed completely as well. That's largely sensible, but is confusing
> >> when users have upgraded and are trying to find out what happened, or how to
> >> configure equivalent functionality.
> > 
> > I don't see the logic in carrying doc stuff that we don't have anymore.
> 
> Well, we do have that already in <tip>'s sprinkled across the docs where it
> makes sense to help transitioning users, like this one in func.sgml:
> 
>     "Prior to PostgreSQL 12, it was possible to skip arbitrary text in the
>     input string using non-letter or non-digit characters..."
> 
> It doesn't seem like a terrible idea to do a similar one for recovery.conf.

I am fine with a tip.  The patch looked like it was creating a new
chapter for it.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee




Commits

  1. Add a docs section for obsoleted and renamed functions and settings