Re: Add docs stub for recovery.conf
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Bruce Momjian <bruce@momjian.us>
Cc: Craig Ringer <craig.ringer@enterprisedb.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-11-11T20:07:39Z
Lists: pgsql-hackers
> On 11 Nov 2020, at 21:01, Bruce Momjian <bruce@momjian.us> wrote: > > 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. I admittedly hadn't looked at the patch, but now that I have I agree with not adding a separate "obsolete" topic for it. I'd prefer to use tips within the docs, they will also help guide users who search for recovery.conf and lands in the tip which is next to the relevant updated documentation on the topic. cheers ./daniel
Commits
-
Add a docs section for obsoleted and renamed functions and settings
- 3b0c647bbfc5 14.0 landed
- 89e383b30a94 13.3 landed
- 448e86c3345b 12.7 landed
- 625f5aae7e42 11.12 landed
- 58960fca4ef1 10.17 landed