Re: documentation structure

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Andrew Dunstan <andrew@dunslane.net>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2024-03-21T16:16:11Z

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 Thu, Mar 21, 2024 at 10:31 AM Robert Haas <robertmhaas@gmail.com> wrote:
> 0001 and 0002 are changed. Should 0002 use the include-an-entity
> approach as well?

Woops. I meant to say that 0001 and 0002 are *unchanged*.

-- 
Robert Haas
EDB: http://www.enterprisedb.com