Re: documentation structure

Peter Eisentraut <peter@eisentraut.org>

From: Peter Eisentraut <peter@eisentraut.org>

To: Robert Haas <robertmhaas@gmail.com>

Cc: Andrew Dunstan <andrew@dunslane.net>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2024-03-22T13:35:47Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

docs: Consistently use <optional> to indicate optional parameters
- 0d829703363b 18.0 landed
docs: Consolidate into new "WAL for Extensions" chapter.
- 09d9800e5282 17.0 landed
freespace: Don't return blocks past the end of the main fork.
- 935829743151 17.0 cited
docs: Merge separate chapters on built-in index AMs into one.
- fe8eaa54420c 17.0 landed
docs: Demote "Monitoring Disk Usage" from chapter to section.
- f470b5c67924 17.0 landed
doc: move system views section to its own chapter
- 64d364bb39cb 16.0 cited

On 22.03.24 13:50, Robert Haas wrote:
> On Thu, Mar 21, 2024 at 7:37 PM Peter Eisentraut <peter@eisentraut.org> wrote:
>> On 20.03.24 17:43, Robert Haas wrote:
>>> 0001 removes the "Installation from Binaries" chapter. The whole thing
>>> is four sentences. I moved the most important information into the
>>> "Installation from Source Code" chapter and retitled it
>>> "Installation".
>>
>> But this separation was explicitly added a few years ago, because most
>> people just want to read about the binaries.
> 
> I really doubt that this is true.

Here is the thread: 
https://www.postgresql.org/message-id/flat/CABUevExRCf8waYOsrCO-QxQL50XGapMf5dnWScOXj7X%3DMXW--g%40mail.gmail.com