Placement of contrib modules in SGML documentation - Mailing list pgsql-docs

From Tom Lane
Subject Placement of contrib modules in SGML documentation
Date
Msg-id 11603.1194755816@sss.pgh.pa.us
Whole thread Raw
Responses Re: Placement of contrib modules in SGML documentation  (Bruce Momjian <bruce@momjian.us>)
Re: Placement of contrib modules in SGML documentation  (Albert Cervera i Areny <albert@nan-tic.com>)
List pgsql-docs
I am still desperately unhappy with the choice to put the contrib docs
where they were put.  They are by no stretch of the imagination part of
the "SQL Language", and there is no defense for having inserted them
into the middle of the part, in front of substantially more widely
interesting information such as concurrency control.

Furthermore, labeling them "Standard Modules" is somebody's flight of
wishful thinking --- if they were installed by default, they'd deserve
such a title, but that's not happening any time soon.

I think there's a case for putting these pages under Part V Server
Programming (though a few are not in fact server-side code), or under
Part VI Reference (ignoring the fact that most of the text isn't in a
uniform reference-page style ... though maybe we could plan to work
towards that) or under Appendixes (though I'm sure there are people
who will complain about that because their private agenda is to make
these things as prominent as possible).  Or we could make them a new
top-level Part, probably just after Reference.

As for the title, how about "Available Add-On Modules", or something
like that?

BTW, why are neither contrib/dblink nor contrib/spi included in the
conversion?

            regards, tom lane

pgsql-docs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: High Availability, Load Balancing, and Replication Feature Matrix
Next
From: Bruce Momjian
Date:
Subject: Re: Placement of contrib modules in SGML documentation