<title>Appendixes</title>
doc/src/sgml/errcodes.sgml doc/src/sgml/datetime.sgml doc/src/sgml/keywords.sgml doc/src/sgml/features.sgml doc/src/sgml/release.sgml
Typical markup:
&<> use & escapes
PostgreSQL <productname>
postgresql.conf, pg_hba.conf <filename>
\<[A-Z][A-Z_ ]+[A-Z_]\> <command>, <literal>, <envar>, <acronym>
\<[A-Za-z_][A-Za-z0-9_]+() <function>
\-\-?[A-Za-z_]+[-A-Za-z_]* <option> (use backslashes to avoid SGML markup)
\<[A-Za-z_]+/[A-Za-z_]+\> <filename>
psql <application>
pg_[A-Za-z0-9_]+ <application>, <structname>
\<[A-Z][A-Z][A-Z_ ]*\> <type>
\<[a-z]+_[a-z_]+\> <varname>, <structfield>
<systemitem class="osname">
wrap long lines
For new features, add links to the documentation sections.
doc/src/sgml/contrib.sgml
These are two separate appendixes because it is difficult to mix regular
sections (for extensions) and refentries (for programs) in one chapter or
appendix. And we do want the programs as refentries so that we can produce man
pages.
doc/src/sgml/external-projects.sgml doc/src/sgml/sourcerepo.sgml doc/src/sgml/docguide.sgml doc/src/sgml/limits.sgml doc/src/sgml/acronyms.sgml doc/src/sgml/color.sgml doc/src/sgml/appendix-obsolete.sgml doc/src/sgml/jpug-doc.sgml