rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
postgresql/doc/src/sgml/filelist.sgml

196 lines
7.8 KiB
Plaintext
Raw Normal View History

Remove cvs keywords from all files.
2010-09-20 22:08:53 +02:00
<!-- doc/src/sgml/filelist.sgml -->
Revive Reference Manual, remove reference pages from User's Guide. Make version.sgml the central place for updating version numbers in the documentation. Document titles now contain the version number of the release they belong to. filelist.sgml is the central (and only) place to declare system entities (i.e., sgml files). No longer a need to declare them in each document header. There is no longer any need to maintain duplicate chapter lists in postgres.sgml and user/admin/etc.sgml, everything is build from the same sources. Some parameter entities allow for different text to be included when the integrated or a single doc set is generated, which eliminates the problems that had caused this to fail in the past.
2000-11-24 18:44:22 +01:00
Uppercase <!ENTITY> and <!DOCTYPE> tags in SGML source This improves compatibility with external toolchains, such as those used by some documentation translation tools. Gabriele Bartolini
2011-04-04 22:07:53 +02:00
<!ENTITY history SYSTEM "history.sgml">
<!ENTITY info SYSTEM "info.sgml">
<!ENTITY intro SYSTEM "intro.sgml">
<!ENTITY legal SYSTEM "legal.sgml">
<!ENTITY notation SYSTEM "notation.sgml">
<!ENTITY problems SYSTEM "problems.sgml">
Revive Reference Manual, remove reference pages from User's Guide. Make version.sgml the central place for updating version numbers in the documentation. Document titles now contain the version number of the release they belong to. filelist.sgml is the central (and only) place to declare system entities (i.e., sgml files). No longer a need to declare them in each document header. There is no longer any need to maintain duplicate chapter lists in postgres.sgml and user/admin/etc.sgml, everything is build from the same sources. Some parameter entities allow for different text to be included when the integrated or a single doc set is generated, which eliminates the problems that had caused this to fail in the past.
2000-11-24 18:44:22 +01:00
<!-- tutorial -->
Uppercase <!ENTITY> and <!DOCTYPE> tags in SGML source This improves compatibility with external toolchains, such as those used by some documentation translation tools. Gabriele Bartolini
2011-04-04 22:07:53 +02:00
<!ENTITY advanced SYSTEM "advanced.sgml">
<!ENTITY query SYSTEM "query.sgml">
<!ENTITY start SYSTEM "start.sgml">
Revive Reference Manual, remove reference pages from User's Guide. Make version.sgml the central place for updating version numbers in the documentation. Document titles now contain the version number of the release they belong to. filelist.sgml is the central (and only) place to declare system entities (i.e., sgml files). No longer a need to declare them in each document header. There is no longer any need to maintain duplicate chapter lists in postgres.sgml and user/admin/etc.sgml, everything is build from the same sources. Some parameter entities allow for different text to be included when the integrated or a single doc set is generated, which eliminates the problems that had caused this to fail in the past.
2000-11-24 18:44:22 +01:00
New blood and fresh air for tutorial
2001-09-03 01:27:50 +02:00
<!-- currently unused, but contains some interesting information -->
Uppercase <!ENTITY> and <!DOCTYPE> tags in SGML source This improves compatibility with external toolchains, such as those used by some documentation translation tools. Gabriele Bartolini
2011-04-04 22:07:53 +02:00
<!ENTITY sql SYSTEM "sql.sgml">
New blood and fresh air for tutorial
2001-09-03 01:27:50 +02:00
Revive Reference Manual, remove reference pages from User's Guide. Make version.sgml the central place for updating version numbers in the documentation. Document titles now contain the version number of the release they belong to. filelist.sgml is the central (and only) place to declare system entities (i.e., sgml files). No longer a need to declare them in each document header. There is no longer any need to maintain duplicate chapter lists in postgres.sgml and user/admin/etc.sgml, everything is build from the same sources. Some parameter entities allow for different text to be included when the integrated or a single doc set is generated, which eliminates the problems that had caused this to fail in the past.
2000-11-24 18:44:22 +01:00
<!-- user's guide -->
Uppercase <!ENTITY> and <!DOCTYPE> tags in SGML source This improves compatibility with external toolchains, such as those used by some documentation translation tools. Gabriele Bartolini
2011-04-04 22:07:53 +02:00
<!ENTITY array SYSTEM "array.sgml">
<!ENTITY datatype SYSTEM "datatype.sgml">
<!ENTITY ddl SYSTEM "ddl.sgml">
<!ENTITY dml SYSTEM "dml.sgml">
<!ENTITY func SYSTEM "func.sgml">
<!ENTITY indices SYSTEM "indices.sgml">
<!ENTITY mvcc SYSTEM "mvcc.sgml">
<!ENTITY perform SYSTEM "perform.sgml">
<!ENTITY queries SYSTEM "queries.sgml">
Return FALSE instead of throwing error for comparisons with empty ranges. Change range_before, range_after, range_adjacent to return false rather than throwing an error when one or both input ranges are empty. The original definition is unnecessarily difficult to use, and also can result in undesirable planner failures since the planner could try to compare an empty range to something else while deriving statistical estimates. (This was, in fact, the cause of repeatable regression test failures on buildfarm member jaguar, as well as intermittent failures elsewhere.) Also tweak rangetypes regression test to not drop all the objects it creates, so that the final state of the regression database contains some rangetype objects for pg_dump testing.
2011-11-14 21:15:53 +01:00
<!ENTITY rangetypes SYSTEM "rangetypes.sgml">
Uppercase <!ENTITY> and <!DOCTYPE> tags in SGML source This improves compatibility with external toolchains, such as those used by some documentation translation tools. Gabriele Bartolini
2011-04-04 22:07:53 +02:00
<!ENTITY rowtypes SYSTEM "rowtypes.sgml">
<!ENTITY syntax SYSTEM "syntax.sgml">
<!ENTITY textsearch SYSTEM "textsearch.sgml">
<!ENTITY typeconv SYSTEM "typeconv.sgml">
Revive Reference Manual, remove reference pages from User's Guide. Make version.sgml the central place for updating version numbers in the documentation. Document titles now contain the version number of the release they belong to. filelist.sgml is the central (and only) place to declare system entities (i.e., sgml files). No longer a need to declare them in each document header. There is no longer any need to maintain duplicate chapter lists in postgres.sgml and user/admin/etc.sgml, everything is build from the same sources. Some parameter entities allow for different text to be included when the integrated or a single doc set is generated, which eliminates the problems that had caused this to fail in the past.
2000-11-24 18:44:22 +01:00
<!-- administrator's guide -->
Uppercase <!ENTITY> and <!DOCTYPE> tags in SGML source This improves compatibility with external toolchains, such as those used by some documentation translation tools. Gabriele Bartolini
2011-04-04 22:07:53 +02:00
<!ENTITY backup SYSTEM "backup.sgml">
<!ENTITY charset SYSTEM "charset.sgml">
<!ENTITY client-auth SYSTEM "client-auth.sgml">
<!ENTITY diskusage SYSTEM "diskusage.sgml">
<!ENTITY high-availability SYSTEM "high-availability.sgml">
<!ENTITY installation SYSTEM "installation.sgml">
<!ENTITY installw SYSTEM "install-windows.sgml">
<!ENTITY maintenance SYSTEM "maintenance.sgml">
<!ENTITY manage-ag SYSTEM "manage-ag.sgml">
<!ENTITY monitoring SYSTEM "monitoring.sgml">
<!ENTITY regress SYSTEM "regress.sgml">
<!ENTITY recovery-config SYSTEM "recovery-config.sgml">
<!ENTITY runtime SYSTEM "runtime.sgml">
<!ENTITY config SYSTEM "config.sgml">
<!ENTITY user-manag SYSTEM "user-manag.sgml">
<!ENTITY wal SYSTEM "wal.sgml">
Revive Reference Manual, remove reference pages from User's Guide. Make version.sgml the central place for updating version numbers in the documentation. Document titles now contain the version number of the release they belong to. filelist.sgml is the central (and only) place to declare system entities (i.e., sgml files). No longer a need to declare them in each document header. There is no longer any need to maintain duplicate chapter lists in postgres.sgml and user/admin/etc.sgml, everything is build from the same sources. Some parameter entities allow for different text to be included when the integrated or a single doc set is generated, which eliminates the problems that had caused this to fail in the past.
2000-11-24 18:44:22 +01:00
<!-- programmer's guide -->
Background worker processes Background workers are postmaster subprocesses that run arbitrary user-specified code. They can request shared memory access as well as backend database connections; or they can just use plain libpq frontend database connections. Modules listed in shared_preload_libraries can register background workers in their _PG_init() function; this is early enough that it's not necessary to provide an extra GUC option, because the necessary extra resources can be allocated early on. Modules can install more than one bgworker, if necessary. Care is taken that these extra processes do not interfere with other postmaster tasks: only one such process is started on each ServerLoop iteration. This means a large number of them could be waiting to be started up and postmaster is still able to quickly service external connection requests. Also, shutdown sequence should not be impacted by a worker process that's reasonably well behaved (i.e. promptly responds to termination signals.) The current implementation lets worker processes specify their start time, i.e. at what point in the server startup process they are to be started: right after postmaster start (in which case they mustn't ask for shared memory access), when consistent state has been reached (useful during recovery in a HOT standby server), or when recovery has terminated (i.e. when normal backends are allowed). In case of a bgworker crash, actions to take depend on registration data: if shared memory was requested, then all other connections are taken down (as well as other bgworkers), just like it were a regular backend crashing. The bgworker itself is restarted, too, within a configurable timeframe (which can be configured to be never). More features to add to this framework can be imagined without much effort, and have been discussed, but this seems good enough as a useful unit already. An elementary sample module is supplied. Author: Álvaro Herrera This patch is loosely based on prior patches submitted by KaiGai Kohei, and unsubmitted code by Simon Riggs. Reviewed by: KaiGai Kohei, Markus Wanner, Andres Freund, Heikki Linnakangas, Simon Riggs, Amit Kapila
2012-12-06 18:57:52 +01:00
<!ENTITY bgworker SYSTEM "bgworker.sgml">
Uppercase <!ENTITY> and <!DOCTYPE> tags in SGML source This improves compatibility with external toolchains, such as those used by some documentation translation tools. Gabriele Bartolini
2011-04-04 22:07:53 +02:00
<!ENTITY dfunc SYSTEM "dfunc.sgml">
<!ENTITY ecpg SYSTEM "ecpg.sgml">
<!ENTITY extend SYSTEM "extend.sgml">
<!ENTITY external-projects SYSTEM "external-projects.sgml">
<!ENTITY func-ref SYSTEM "func-ref.sgml">
<!ENTITY infoschema SYSTEM "information_schema.sgml">
<!ENTITY libpq SYSTEM "libpq.sgml">
<!ENTITY lobj SYSTEM "lobj.sgml">
<!ENTITY rules SYSTEM "rules.sgml">
<!ENTITY spi SYSTEM "spi.sgml">
<!ENTITY trigger SYSTEM "trigger.sgml">
Syntax support and documentation for event triggers. They don't actually do anything yet; that will get fixed in a follow-on commit. But this gets the basic infrastructure in place, including CREATE/ALTER/DROP EVENT TRIGGER; support for COMMENT, SECURITY LABEL, and ALTER EXTENSION .. ADD/DROP EVENT TRIGGER; pg_dump and psql support; and documentation for the anticipated initial feature set. Dimitri Fontaine, with review and a bunch of additional hacking by me. Thom Brown extensively reviewed earlier versions of this patch set, but there's not a whole lot of that code left in this commit, as it turns out.
2012-07-18 16:16:16 +02:00
<!ENTITY event-trigger SYSTEM "event-trigger.sgml">
Uppercase <!ENTITY> and <!DOCTYPE> tags in SGML source This improves compatibility with external toolchains, such as those used by some documentation translation tools. Gabriele Bartolini
2011-04-04 22:07:53 +02:00
<!ENTITY xaggr SYSTEM "xaggr.sgml">
<!ENTITY xfunc SYSTEM "xfunc.sgml">
<!ENTITY xindex SYSTEM "xindex.sgml">
<!ENTITY xplang SYSTEM "xplang.sgml">
<!ENTITY xoper SYSTEM "xoper.sgml">
<!ENTITY xtypes SYSTEM "xtypes.sgml">
<!ENTITY plperl SYSTEM "plperl.sgml">
<!ENTITY plpython SYSTEM "plpython.sgml">
<!ENTITY plsql SYSTEM "plpgsql.sgml">
<!ENTITY pltcl SYSTEM "pltcl.sgml">
Revive Reference Manual, remove reference pages from User's Guide. Make version.sgml the central place for updating version numbers in the documentation. Document titles now contain the version number of the release they belong to. filelist.sgml is the central (and only) place to declare system entities (i.e., sgml files). No longer a need to declare them in each document header. There is no longer any need to maintain duplicate chapter lists in postgres.sgml and user/admin/etc.sgml, everything is build from the same sources. Some parameter entities allow for different text to be included when the integrated or a single doc set is generated, which eliminates the problems that had caused this to fail in the past.
2000-11-24 18:44:22 +01:00
Move docs about index cost estimation functions and writing a procedural language handler to the 'Internals' area, per my proposal of yesterday. Clean up the trigger documentation a bit. Push SPI chapter to the end of its part, and reorder the Internals chapters into what seems a more sensible order (at the moment anyway).
2003-10-23 00:28:10 +02:00
<!-- reference pages -->
Uppercase <!ENTITY> and <!DOCTYPE> tags in SGML source This improves compatibility with external toolchains, such as those used by some documentation translation tools. Gabriele Bartolini
2011-04-04 22:07:53 +02:00
<!ENTITY % allfiles SYSTEM "ref/allfiles.sgml">
Move docs about index cost estimation functions and writing a procedural language handler to the 'Internals' area, per my proposal of yesterday. Clean up the trigger documentation a bit. Push SPI chapter to the end of its part, and reorder the Internals chapters into what seems a more sensible order (at the moment anyway).
2003-10-23 00:28:10 +02:00
%allfiles;
Revive Reference Manual, remove reference pages from User's Guide. Make version.sgml the central place for updating version numbers in the documentation. Document titles now contain the version number of the release they belong to. filelist.sgml is the central (and only) place to declare system entities (i.e., sgml files). No longer a need to declare them in each document header. There is no longer any need to maintain duplicate chapter lists in postgres.sgml and user/admin/etc.sgml, everything is build from the same sources. Some parameter entities allow for different text to be included when the integrated or a single doc set is generated, which eliminates the problems that had caused this to fail in the past.
2000-11-24 18:44:22 +01:00
<!-- developer's guide -->
Uppercase <!ENTITY> and <!DOCTYPE> tags in SGML source This improves compatibility with external toolchains, such as those used by some documentation translation tools. Gabriele Bartolini
2011-04-04 22:07:53 +02:00
<!ENTITY arch-dev SYSTEM "arch-dev.sgml">
<!ENTITY bki SYSTEM "bki.sgml">
<!ENTITY catalogs SYSTEM "catalogs.sgml">
<!ENTITY geqo SYSTEM "geqo.sgml">
<!ENTITY gist SYSTEM "gist.sgml">
Add SP-GiST (space-partitioned GiST) index access method. SP-GiST is comparable to GiST in flexibility, but supports non-balanced partitioned search structures rather than balanced trees. As described at PGCon 2011, this new indexing structure can beat GiST in both index build time and query speed for search problems that it is well matched to. There are a number of areas that could still use improvement, but at this point the code seems committable. Teodor Sigaev and Oleg Bartunov, with considerable revisions by Tom Lane
2011-12-17 22:41:16 +01:00
<!ENTITY spgist SYSTEM "spgist.sgml">
Uppercase <!ENTITY> and <!DOCTYPE> tags in SGML source This improves compatibility with external toolchains, such as those used by some documentation translation tools. Gabriele Bartolini
2011-04-04 22:07:53 +02:00
<!ENTITY gin SYSTEM "gin.sgml">
<!ENTITY planstats SYSTEM "planstats.sgml">
<!ENTITY indexam SYSTEM "indexam.sgml">
<!ENTITY nls SYSTEM "nls.sgml">
<!ENTITY plhandler SYSTEM "plhandler.sgml">
<!ENTITY fdwhandler SYSTEM "fdwhandler.sgml">
<!ENTITY protocol SYSTEM "protocol.sgml">
<!ENTITY sources SYSTEM "sources.sgml">
<!ENTITY storage SYSTEM "storage.sgml">
Move docs about index cost estimation functions and writing a procedural language handler to the 'Internals' area, per my proposal of yesterday. Clean up the trigger documentation a bit. Push SPI chapter to the end of its part, and reorder the Internals chapters into what seems a more sensible order (at the moment anyway).
2003-10-23 00:28:10 +02:00
Move most /contrib README files into SGML. Some still need conversion or will never be converted.
2007-11-11 00:30:46 +01:00
<!-- contrib information -->
Uppercase <!ENTITY> and <!DOCTYPE> tags in SGML source This improves compatibility with external toolchains, such as those used by some documentation translation tools. Gabriele Bartolini
2011-04-04 22:07:53 +02:00
<!ENTITY contrib SYSTEM "contrib.sgml">
<!ENTITY adminpack SYSTEM "adminpack.sgml">
<!ENTITY auth-delay SYSTEM "auth-delay.sgml">
<!ENTITY auto-explain SYSTEM "auto-explain.sgml">
<!ENTITY btree-gin SYSTEM "btree-gin.sgml">
<!ENTITY btree-gist SYSTEM "btree-gist.sgml">
<!ENTITY chkpass SYSTEM "chkpass.sgml">
<!ENTITY citext SYSTEM "citext.sgml">
<!ENTITY cube SYSTEM "cube.sgml">
<!ENTITY dblink SYSTEM "dblink.sgml">
<!ENTITY dict-int SYSTEM "dict-int.sgml">
<!ENTITY dict-xsyn SYSTEM "dict-xsyn.sgml">
<!ENTITY dummy-seclabel SYSTEM "dummy-seclabel.sgml">
<!ENTITY earthdistance SYSTEM "earthdistance.sgml">
<!ENTITY file-fdw SYSTEM "file-fdw.sgml">
<!ENTITY fuzzystrmatch SYSTEM "fuzzystrmatch.sgml">
<!ENTITY hstore SYSTEM "hstore.sgml">
<!ENTITY intagg SYSTEM "intagg.sgml">
<!ENTITY intarray SYSTEM "intarray.sgml">
<!ENTITY isn SYSTEM "isn.sgml">
<!ENTITY lo SYSTEM "lo.sgml">
<!ENTITY ltree SYSTEM "ltree.sgml">
<!ENTITY oid2name SYSTEM "oid2name.sgml">
<!ENTITY pageinspect SYSTEM "pageinspect.sgml">
<!ENTITY passwordcheck SYSTEM "passwordcheck.sgml">
<!ENTITY pgbench SYSTEM "pgbench.sgml">
<!ENTITY pgarchivecleanup SYSTEM "pgarchivecleanup.sgml">
<!ENTITY pgbuffercache SYSTEM "pgbuffercache.sgml">
<!ENTITY pgcrypto SYSTEM "pgcrypto.sgml">
<!ENTITY pgfreespacemap SYSTEM "pgfreespacemap.sgml">
<!ENTITY pgrowlocks SYSTEM "pgrowlocks.sgml">
<!ENTITY pgstandby SYSTEM "pgstandby.sgml">
<!ENTITY pgstatstatements SYSTEM "pgstatstatements.sgml">
<!ENTITY pgstattuple SYSTEM "pgstattuple.sgml">
<!ENTITY pgtestfsync SYSTEM "pgtestfsync.sgml">
pg_test_timing utility, to measure clock monotonicity and timing cost. Ants Aasma, Greg Smith
2012-03-27 22:14:00 +02:00
<!ENTITY pgtesttiming SYSTEM "pgtesttiming.sgml">
Uppercase <!ENTITY> and <!DOCTYPE> tags in SGML source This improves compatibility with external toolchains, such as those used by some documentation translation tools. Gabriele Bartolini
2011-04-04 22:07:53 +02:00
<!ENTITY pgtrgm SYSTEM "pgtrgm.sgml">
<!ENTITY pgupgrade SYSTEM "pgupgrade.sgml">
<!ENTITY seg SYSTEM "seg.sgml">
<!ENTITY contrib-spi SYSTEM "contrib-spi.sgml">
<!ENTITY sepgsql SYSTEM "sepgsql.sgml">
<!ENTITY sslinfo SYSTEM "sslinfo.sgml">
<!ENTITY tablefunc SYSTEM "tablefunc.sgml">
Triggered change notifications. Kevin Grittner, reviewed (in earlier versions) by Álvaro Herrera
2012-01-20 05:15:15 +01:00
<!ENTITY tcn SYSTEM "tcn.sgml">
Uppercase <!ENTITY> and <!DOCTYPE> tags in SGML source This improves compatibility with external toolchains, such as those used by some documentation translation tools. Gabriele Bartolini
2011-04-04 22:07:53 +02:00
<!ENTITY test-parser SYSTEM "test-parser.sgml">
<!ENTITY tsearch2 SYSTEM "tsearch2.sgml">
<!ENTITY unaccent SYSTEM "unaccent.sgml">
<!ENTITY uuid-ossp SYSTEM "uuid-ossp.sgml">
<!ENTITY vacuumlo SYSTEM "vacuumlo.sgml">
<!ENTITY xml2 SYSTEM "xml2.sgml">
Move most /contrib README files into SGML. Some still need conversion or will never be converted.
2007-11-11 00:30:46 +01:00
Move docs about index cost estimation functions and writing a procedural language handler to the 'Internals' area, per my proposal of yesterday. Clean up the trigger documentation a bit. Push SPI chapter to the end of its part, and reorder the Internals chapters into what seems a more sensible order (at the moment anyway).
2003-10-23 00:28:10 +02:00
<!-- appendixes -->
Uppercase <!ENTITY> and <!DOCTYPE> tags in SGML source This improves compatibility with external toolchains, such as those used by some documentation translation tools. Gabriele Bartolini
2011-04-04 22:07:53 +02:00
<!ENTITY contacts SYSTEM "contacts.sgml">
<!ENTITY datetime SYSTEM "datetime.sgml">
<!ENTITY docguide SYSTEM "docguide.sgml">
<!ENTITY errcodes SYSTEM "errcodes.sgml">
<!ENTITY features SYSTEM "features.sgml">
<!ENTITY keywords SYSTEM "keywords.sgml">
<!ENTITY sourcerepo SYSTEM "sourcerepo.sgml">
<!ENTITY release SYSTEM "release.sgml">
Publish draft version of Postgres 9.2 release notes.
2012-05-10 04:25:43 +02:00
<!ENTITY release-9.2 SYSTEM "release-9.2.sgml">
Uppercase <!ENTITY> and <!DOCTYPE> tags in SGML source This improves compatibility with external toolchains, such as those used by some documentation translation tools. Gabriele Bartolini
2011-04-04 22:07:53 +02:00
<!ENTITY release-9.1 SYSTEM "release-9.1.sgml">
<!ENTITY release-9.0 SYSTEM "release-9.0.sgml">
<!ENTITY release-8.4 SYSTEM "release-8.4.sgml">
<!ENTITY release-8.3 SYSTEM "release-8.3.sgml">
<!ENTITY release-8.2 SYSTEM "release-8.2.sgml">
<!ENTITY release-8.1 SYSTEM "release-8.1.sgml">
<!ENTITY release-8.0 SYSTEM "release-8.0.sgml">
<!ENTITY release-7.4 SYSTEM "release-7.4.sgml">
<!ENTITY release-old SYSTEM "release-old.sgml">
<!ENTITY acronyms SYSTEM "acronyms.sgml">
<!ENTITY features-supported SYSTEM "features-supported.sgml">
<!ENTITY features-unsupported SYSTEM "features-unsupported.sgml">
<!ENTITY errcodes-table SYSTEM "errcodes-table.sgml">
Avoid maintaining three separate copies of the error codes list. src/pl/plpgsql/src/plerrcodes.h, src/include/utils/errcodes.h, and a big chunk of errcodes.sgml are now automatically generated from a single file, src/backend/utils/errcodes.txt. Jan Urbański, reviewed by Tom Lane.
2011-02-04 04:32:49 +01:00
Move docs about index cost estimation functions and writing a procedural language handler to the 'Internals' area, per my proposal of yesterday. Clean up the trigger documentation a bit. Push SPI chapter to the end of its part, and reorder the Internals chapters into what seems a more sensible order (at the moment anyway).
2003-10-23 00:28:10 +02:00
<!-- back matter -->
Uppercase <!ENTITY> and <!DOCTYPE> tags in SGML source This improves compatibility with external toolchains, such as those used by some documentation translation tools. Gabriele Bartolini
2011-04-04 22:07:53 +02:00
<!ENTITY biblio SYSTEM "biblio.sgml">
<!ENTITY bookindex SYSTEM "bookindex.sgml">
Revive Reference Manual, remove reference pages from User's Guide. Make version.sgml the central place for updating version numbers in the documentation. Document titles now contain the version number of the release they belong to. filelist.sgml is the central (and only) place to declare system entities (i.e., sgml files). No longer a need to declare them in each document header. There is no longer any need to maintain duplicate chapter lists in postgres.sgml and user/admin/etc.sgml, everything is build from the same sources. Some parameter entities allow for different text to be included when the integrated or a single doc set is generated, which eliminates the problems that had caused this to fail in the past.
2000-11-24 18:44:22 +01:00
Readd test/regress/README file, this time with a well-defined and simple rule to remake it when necessary.
2001-09-21 20:37:05 +02:00
<!--
Some parts of the documentation are also source for some plain-text
files used during installation. To selectively ignore or include
some parts (e.g., external xref's) when generating these files we use
these parameter entities. See also standalone-install.sgml.
-->
Uppercase <!ENTITY> and <!DOCTYPE> tags in SGML source This improves compatibility with external toolchains, such as those used by some documentation translation tools. Gabriele Bartolini
2011-04-04 22:07:53 +02:00
<!ENTITY % standalone-ignore "INCLUDE">
<!ENTITY % standalone-include "IGNORE">
Rearrangement of the HTML docs build rules Set up proper makefile dependencies in the documentation build rules, especially around the HTML/index build. The problem we've had with all previous solutions is that we have used the same file name, such as HTML.index or bookindex.sgml, to mean different things at different stages of the build, and make can't distinguish that. The solution here is that the first jade run produces HTML.index, but does not require bookindex.sgml at all, and produces no other html output (the latter an idea from Alvaro). The second jade run includes bookindex.sgml, but does not recreate HTML.index. That way, when you change an sgml file, jade is run twice and at the end all dependencies are satisfied. Omitting the html output in the first stage also makes the full build a lot faster. When you run one of the print format targets, only the first jade run is run, then the print target-specific commands. If an HTML build has completed previously, the first jade run is skipped because the dependencies have already been satisfied. The draft and check targets for quick builds and syntax verification are still there.
2009-07-15 00:16:38 +02:00
<!--
By default, no index is included. Use -i include-index on the command line
to include it.
-->
Uppercase <!ENTITY> and <!DOCTYPE> tags in SGML source This improves compatibility with external toolchains, such as those used by some documentation translation tools. Gabriele Bartolini
2011-04-04 22:07:53 +02:00
<!ENTITY % include-index "IGNORE">