Re: documentation structure

Tatsuo Ishii <ishii@postgresql.org>

From: Tatsuo Ishii <ishii@postgresql.org>

To: andrew@dunslane.net

Cc: corey.huinker@gmail.com, jian.universality@gmail.com, robertmhaas@gmail.com, pgsql-hackers@postgresql.org

Date: 2024-07-19T03:06:22Z

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

> I'm opposed to having a separate file for every function. I think
> breaking up func.sgml into one piece per sect1 is about right. If that
> proves cumbersome still we can look at breaking it up further, but
> let's start with that.

That will create at least 30 func-xx.sgml files.

t-ishii$ grep '<sect1' func.sgml|wc -l
30

I am afraid that's too many?

Best reagards,
--
Tatsuo Ishii
SRA OSS LLC
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp