2010-09-20 22:08:53 +02:00
|
|
|
<!-- doc/src/sgml/filelist.sgml -->
|
2000-11-24 18:44:22 +01:00
|
|
|
|
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">
|
2000-11-24 18:44:22 +01:00
|
|
|
|
|
|
|
<!-- tutorial -->
|
2011-04-04 22:07:53 +02:00
|
|
|
<!ENTITY advanced SYSTEM "advanced.sgml">
|
|
|
|
<!ENTITY query SYSTEM "query.sgml">
|
|
|
|
<!ENTITY start SYSTEM "start.sgml">
|
2000-11-24 18:44:22 +01:00
|
|
|
|
2001-09-03 01:27:50 +02:00
|
|
|
<!-- currently unused, but contains some interesting information -->
|
2011-04-04 22:07:53 +02:00
|
|
|
<!ENTITY sql SYSTEM "sql.sgml">
|
2001-09-03 01:27:50 +02:00
|
|
|
|
2000-11-24 18:44:22 +01:00
|
|
|
<!-- user's guide -->
|
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">
|
Introduce jsonb, a structured format for storing json.
The new format accepts exactly the same data as the json type. However, it is
stored in a format that does not require reparsing the orgiginal text in order
to process it, making it much more suitable for indexing and other operations.
Insignificant whitespace is discarded, and the order of object keys is not
preserved. Neither are duplicate object keys kept - the later value for a given
key is the only one stored.
The new type has all the functions and operators that the json type has,
with the exception of the json generation functions (to_json, json_agg etc.)
and with identical semantics. In addition, there are operator classes for
hash and btree indexing, and two classes for GIN indexing, that have no
equivalent in the json type.
This feature grew out of previous work by Oleg Bartunov and Teodor Sigaev, which
was intended to provide similar facilities to a nested hstore type, but which
in the end proved to have some significant compatibility issues.
Authors: Oleg Bartunov, Teodor Sigaev, Peter Geoghegan and Andrew Dunstan.
Review: Andres Freund
2014-03-23 21:40:19 +01:00
|
|
|
<!ENTITY json SYSTEM "json.sgml">
|
2011-04-04 22:07:53 +02:00
|
|
|
<!ENTITY mvcc SYSTEM "mvcc.sgml">
|
2016-09-21 14:37:02 +02:00
|
|
|
<!ENTITY parallel SYSTEM "parallel.sgml">
|
2011-04-04 22:07:53 +02:00
|
|
|
<!ENTITY perform SYSTEM "perform.sgml">
|
|
|
|
<!ENTITY queries SYSTEM "queries.sgml">
|
2011-11-14 21:15:53 +01:00
|
|
|
<!ENTITY rangetypes SYSTEM "rangetypes.sgml">
|
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">
|
2000-11-24 18:44:22 +01:00
|
|
|
|
|
|
|
<!-- administrator's guide -->
|
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">
|
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">
|
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">
|
2012-07-18 16:16:16 +02:00
|
|
|
<!ENTITY event-trigger SYSTEM "event-trigger.sgml">
|
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">
|
2000-11-24 18:44:22 +01:00
|
|
|
|
2003-10-23 00:28:10 +02:00
|
|
|
<!-- reference pages -->
|
2011-04-04 22:07:53 +02:00
|
|
|
<!ENTITY % allfiles SYSTEM "ref/allfiles.sgml">
|
2003-10-23 00:28:10 +02:00
|
|
|
%allfiles;
|
|
|
|
|
2000-11-24 18:44:22 +01:00
|
|
|
<!-- developer's guide -->
|
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">
|
2011-12-17 22:41:16 +01:00
|
|
|
<!ENTITY spgist SYSTEM "spgist.sgml">
|
2011-04-04 22:07:53 +02:00
|
|
|
<!ENTITY gin SYSTEM "gin.sgml">
|
BRIN: Block Range Indexes
BRIN is a new index access method intended to accelerate scans of very
large tables, without the maintenance overhead of btrees or other
traditional indexes. They work by maintaining "summary" data about
block ranges. Bitmap index scans work by reading each summary tuple and
comparing them with the query quals; all pages in the range are returned
in a lossy TID bitmap if the quals are consistent with the values in the
summary tuple, otherwise not. Normal index scans are not supported
because these indexes do not store TIDs.
As new tuples are added into the index, the summary information is
updated (if the block range in which the tuple is added is already
summarized) or not; in the latter case, a subsequent pass of VACUUM or
the brin_summarize_new_values() function will create the summary
information.
For data types with natural 1-D sort orders, the summary info consists
of the maximum and the minimum values of each indexed column within each
page range. This type of operator class we call "Minmax", and we
supply a bunch of them for most data types with B-tree opclasses.
Since the BRIN code is generalized, other approaches are possible for
things such as arrays, geometric types, ranges, etc; even for things
such as enum types we could do something different than minmax with
better results. In this commit I only include minmax.
Catalog version bumped due to new builtin catalog entries.
There's more that could be done here, but this is a good step forwards.
Loosely based on ideas from Simon Riggs; code mostly by Álvaro Herrera,
with contribution by Heikki Linnakangas.
Patch reviewed by: Amit Kapila, Heikki Linnakangas, Robert Haas.
Testing help from Jeff Janes, Erik Rijkers, Emanuel Calvo.
PS:
The research leading to these results has received funding from the
European Union's Seventh Framework Programme (FP7/2007-2013) under
grant agreement n° 318633.
2014-11-07 20:38:14 +01:00
|
|
|
<!ENTITY brin SYSTEM "brin.sgml">
|
2011-04-04 22:07:53 +02:00
|
|
|
<!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">
|
2015-03-13 12:55:39 +01:00
|
|
|
<!ENTITY custom-scan SYSTEM "custom-scan.sgml">
|
2014-03-18 18:20:01 +01:00
|
|
|
<!ENTITY logicaldecoding SYSTEM "logicaldecoding.sgml">
|
Introduce replication progress tracking infrastructure.
When implementing a replication solution ontop of logical decoding, two
related problems exist:
* How to safely keep track of replication progress
* How to change replication behavior, based on the origin of a row;
e.g. to avoid loops in bi-directional replication setups
The solution to these problems, as implemented here, consist out of
three parts:
1) 'replication origins', which identify nodes in a replication setup.
2) 'replication progress tracking', which remembers, for each
replication origin, how far replay has progressed in a efficient and
crash safe manner.
3) The ability to filter out changes performed on the behest of a
replication origin during logical decoding; this allows complex
replication topologies. E.g. by filtering all replayed changes out.
Most of this could also be implemented in "userspace", e.g. by inserting
additional rows contain origin information, but that ends up being much
less efficient and more complicated. We don't want to require various
replication solutions to reimplement logic for this independently. The
infrastructure is intended to be generic enough to be reusable.
This infrastructure also replaces the 'nodeid' infrastructure of commit
timestamps. It is intended to provide all the former capabilities,
except that there's only 2^16 different origins; but now they integrate
with logical decoding. Additionally more functionality is accessible via
SQL. Since the commit timestamp infrastructure has also been introduced
in 9.5 (commit 73c986add) changing the API is not a problem.
For now the number of origins for which the replication progress can be
tracked simultaneously is determined by the max_replication_slots
GUC. That GUC is not a perfect match to configure this, but there
doesn't seem to be sufficient reason to introduce a separate new one.
Bumps both catversion and wal page magic.
Author: Andres Freund, with contributions from Petr Jelinek and Craig Ringer
Reviewed-By: Heikki Linnakangas, Petr Jelinek, Robert Haas, Steve Singer
Discussion: 20150216002155.GI15326@awork2.anarazel.de,
20140923182422.GA15776@alap3.anarazel.de,
20131114172632.GE7522@alap2.anarazel.de
2015-04-29 19:30:53 +02:00
|
|
|
<!ENTITY replication-origins SYSTEM "replication-origins.sgml">
|
2011-04-04 22:07:53 +02:00
|
|
|
<!ENTITY protocol SYSTEM "protocol.sgml">
|
|
|
|
<!ENTITY sources SYSTEM "sources.sgml">
|
|
|
|
<!ENTITY storage SYSTEM "storage.sgml">
|
2015-05-15 21:40:52 +02:00
|
|
|
<!ENTITY tablesample-method SYSTEM "tablesample-method.sgml">
|
2016-04-01 11:21:48 +02:00
|
|
|
<!ENTITY generic-wal SYSTEM "generic-wal.sgml">
|
2003-10-23 00:28:10 +02:00
|
|
|
|
2007-11-11 00:30:46 +01:00
|
|
|
<!-- contrib information -->
|
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">
|
2016-04-01 15:42:24 +02:00
|
|
|
<!ENTITY bloom SYSTEM "bloom.sgml">
|
2011-04-04 22:07:53 +02:00
|
|
|
<!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 pgbuffercache SYSTEM "pgbuffercache.sgml">
|
|
|
|
<!ENTITY pgcrypto SYSTEM "pgcrypto.sgml">
|
|
|
|
<!ENTITY pgfreespacemap SYSTEM "pgfreespacemap.sgml">
|
2013-12-20 14:08:01 +01:00
|
|
|
<!ENTITY pgprewarm SYSTEM "pgprewarm.sgml">
|
2011-04-04 22:07:53 +02:00
|
|
|
<!ENTITY pgrowlocks SYSTEM "pgrowlocks.sgml">
|
|
|
|
<!ENTITY pgstandby SYSTEM "pgstandby.sgml">
|
|
|
|
<!ENTITY pgstatstatements SYSTEM "pgstatstatements.sgml">
|
|
|
|
<!ENTITY pgstattuple SYSTEM "pgstattuple.sgml">
|
|
|
|
<!ENTITY pgtrgm SYSTEM "pgtrgm.sgml">
|
2016-03-08 14:38:50 +01:00
|
|
|
<!ENTITY pgvisibility SYSTEM "pgvisibility.sgml">
|
2013-02-21 11:26:23 +01:00
|
|
|
<!ENTITY postgres-fdw SYSTEM "postgres-fdw.sgml">
|
2011-04-04 22:07:53 +02:00
|
|
|
<!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">
|
2012-01-20 05:15:15 +01:00
|
|
|
<!ENTITY tcn SYSTEM "tcn.sgml">
|
Introduce logical decoding.
This feature, building on previous commits, allows the write-ahead log
stream to be decoded into a series of logical changes; that is,
inserts, updates, and deletes and the transactions which contain them.
It is capable of handling decoding even across changes to the schema
of the effected tables. The output format is controlled by a
so-called "output plugin"; an example is included. To make use of
this in a real replication system, the output plugin will need to be
modified to produce output in the format appropriate to that system,
and to perform filtering.
Currently, information can be extracted from the logical decoding
system only via SQL; future commits will add the ability to stream
changes via walsender.
Andres Freund, with review and other contributions from many other
people, including Álvaro Herrera, Abhijit Menon-Sen, Peter Gheogegan,
Kevin Grittner, Robert Haas, Heikki Linnakangas, Fujii Masao, Abhijit
Menon-Sen, Michael Paquier, Simon Riggs, Craig Ringer, and Steve
Singer.
2014-03-03 22:32:18 +01:00
|
|
|
<!ENTITY test-decoding SYSTEM "test-decoding.sgml">
|
2011-04-04 22:07:53 +02:00
|
|
|
<!ENTITY test-parser SYSTEM "test-parser.sgml">
|
2014-01-14 21:58:15 +01:00
|
|
|
<!ENTITY test-shm-mq SYSTEM "test-shm-mq.sgml">
|
2011-04-04 22:07:53 +02:00
|
|
|
<!ENTITY tsearch2 SYSTEM "tsearch2.sgml">
|
2015-05-15 21:14:22 +02:00
|
|
|
<!ENTITY tsm-system-rows SYSTEM "tsm-system-rows.sgml">
|
2015-05-15 21:18:57 +02:00
|
|
|
<!ENTITY tsm-system-time SYSTEM "tsm-system-time.sgml">
|
2011-04-04 22:07:53 +02:00
|
|
|
<!ENTITY unaccent SYSTEM "unaccent.sgml">
|
|
|
|
<!ENTITY uuid-ossp SYSTEM "uuid-ossp.sgml">
|
|
|
|
<!ENTITY vacuumlo SYSTEM "vacuumlo.sgml">
|
|
|
|
<!ENTITY xml2 SYSTEM "xml2.sgml">
|
2007-11-11 00:30:46 +01:00
|
|
|
|
2003-10-23 00:28:10 +02:00
|
|
|
<!-- appendixes -->
|
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">
|
2016-05-05 19:27:59 +02:00
|
|
|
<!ENTITY release-9.6 SYSTEM "release-9.6.sgml">
|
2015-06-11 06:08:55 +02:00
|
|
|
<!ENTITY release-9.5 SYSTEM "release-9.5.sgml">
|
2014-05-04 05:16:24 +02:00
|
|
|
<!ENTITY release-9.4 SYSTEM "release-9.4.sgml">
|
2013-04-20 22:29:58 +02:00
|
|
|
<!ENTITY release-9.3 SYSTEM "release-9.3.sgml">
|
2012-05-10 04:25:43 +02:00
|
|
|
<!ENTITY release-9.2 SYSTEM "release-9.2.sgml">
|
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">
|
2011-02-04 04:32:49 +01:00
|
|
|
|
2003-10-23 00:28:10 +02:00
|
|
|
<!-- back matter -->
|
2011-04-04 22:07:53 +02:00
|
|
|
<!ENTITY biblio SYSTEM "biblio.sgml">
|
|
|
|
<!ENTITY bookindex SYSTEM "bookindex.sgml">
|
2000-11-24 18:44:22 +01:00
|
|
|
|
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.
|
|
|
|
-->
|
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.
|
|
|
|
-->
|
2011-04-04 22:07:53 +02:00
|
|
|
<!ENTITY % include-index "IGNORE">
|
2013-10-16 04:54:36 +02:00
|
|
|
|
|
|
|
<!--
|
|
|
|
Create empty index element for processing by XSLT stylesheet.
|
|
|
|
-->
|
|
|
|
<!ENTITY % include-xslt-index "IGNORE">
|