Horton

Re: documentation structure

Peter Eisentraut <peter@eisentraut.org>

View thread
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-04-08T14:15:29Z
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 →

  1. docs: Consistently use <optional> to indicate optional parameters

  2. docs: Consolidate into new "WAL for Extensions" chapter.

  3. freespace: Don't return blocks past the end of the main fork.

  4. docs: Merge separate chapters on built-in index AMs into one.

  5. docs: Demote "Monitoring Disk Usage" from chapter to section.

  6. doc: move system views section to its own chapter

On 05.04.24 17:11, Robert Haas wrote:
>> 4. Consolidate the "Generic WAL Records" and "Custom WAL Resource
>> Managers" chapters, which cover related topics, into a single one. I
>> didn't see anyone object to this, but David Johnston pointed out that
>> the patch I posted was a few bricks short of a load, because it really
>> needed to put some introductory text into the new chapter. I'll study
>> this a bit more and propose a new patch that does the same thing a bit
>> more carefully than my previous version did.
> 
> Here is a new version of this patch. I think this is v18 material at
> this point, absent an outcry to the contrary. Sometimes we're flexible
> about doc patches.

Looks good to me.  I think this could go into PG17.