| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Tristan Partin <tristan(at)partin(dot)io>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Subject: | Re: man3 Documentation |
| Date: | 2026-08-05 16:38:30 |
| Message-ID: | anNlnqNQEJ4OJ0P8@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2026-Aug-05, Peter Eisentraut wrote:
> On 04.08.26 20:52, Tristan Partin wrote:
> > Out of curiosity, I was trying to understand what man pages we generate.
> > I found man pgaes for the executables in man1 and a ton of documentation
> > in man7 related to SQL commands. The contents in man3 was a bit
> > perplexing. We only document a set of dblink SQL functions and a set of
> > SPI C functions.
>
> Man pages are produced for all refentry markup. If you want to add more,
> you would have to format the material to fit into that schema. I think
> proposals for more man pages could be considered.
A few months ago I looked into changing the libpq documentation to
refentry format specifically to get a manpage for each function.
Eventually I decided not to do anything because most of them were way
too short and it looked a bit odd, and the current format is too
different from what the end shape would have to be. But maybe it's not
that bad. In principle I +1 the idea for libpq.
Not sure what else would be appropriate to turn into refentry, but I'd
say let's start with one section.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rui Zhao | 2026-08-05 16:44:11 | Re: lost lock during toasting allows fk violation |
| Previous Message | Masahiko Sawada | 2026-08-05 16:32:19 | Re: Add a hook for handling logical decoding messages on subscribers. |