postgres-xc-committers Mailing List for Postgres-XC

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Project "Postgres-XC".

The branch, documentation has been updated
       via  1dc1b90e434dbe56438dec9dfa8887de1767d457 (commit)
      from  58954e79e274b1280329aa61ca6af66b88c59cf6 (commit)


- Log -----------------------------------------------------------------
commit 1dc1b90e434dbe56438dec9dfa8887de1767d457
Author: Koichi Suzuki <koi...@gm...>
Date:   Mon May 16 18:30:02 2011 +0900

    This commit corrects the initial notify for each document source to mark
    what section is from PostgreSQL and needs review/revision for Postgres-XC.
    
    Next work is to review each section and revise it as Postgres-XC
    documentation.
    
    This will be done in the following order:
    
    1. Installation/Cluster configuration/Cluster admninistration,
    2. Statements,
    3. Tutorials,
    4. Application interface.
    
    All the source files are affected.

diff --git a/doc/src/sgml/acronyms.sgmlin b/doc/src/sgml/acronyms.sgmlin
index de4e1e0..8d1cab6 100644
--- a/doc/src/sgml/acronyms.sgmlin
+++ b/doc/src/sgml/acronyms.sgmlin
@@ -2,6 +2,7 @@
 
 <appendix id="acronyms">
  <title>Acronyms</title>
+  &pgnotice;
 
  <para>
   This is a list of acronyms commonly used in the <productname>PostgreSQL</>
diff --git a/doc/src/sgml/adminpack.sgmlin b/doc/src/sgml/adminpack.sgmlin
index b097000..4ec8c99 100644
--- a/doc/src/sgml/adminpack.sgmlin
+++ b/doc/src/sgml/adminpack.sgmlin
@@ -6,6 +6,7 @@
  <indexterm zone="adminpack">
   <primary>adminpack</primary>
  </indexterm>
+  &pgnotice;
 
  <para>
   <filename>adminpack</> provides a number of support functions which
@@ -16,7 +17,7 @@
 
  <sect2>
   <title>Functions implemented</title>
-
+  &pgnotice;
   <para>
    The functions implemented by <filename>adminpack</> can only be run by a
    superuser. Here's a list of these functions:
diff --git a/doc/src/sgml/advanced.sgmlin b/doc/src/sgml/advanced.sgmlin
index 38045b5..ab7e1dd 100644
--- a/doc/src/sgml/advanced.sgmlin
+++ b/doc/src/sgml/advanced.sgmlin
@@ -5,6 +5,7 @@
 
   <sect1 id="tutorial-advanced-intro">
    <title>Introduction</title>
+  &pgnotice;
 
    <para>
     In the previous chapter we have covered the basics of using
@@ -35,6 +36,7 @@
    <indexterm zone="tutorial-views">
     <primary>view</primary>
    </indexterm>
+  &pgnotice;
 
    <para>
     Refer back to the queries in <xref linkend="tutorial-join">.
@@ -78,6 +80,7 @@ SELECT * FROM myview;
    <indexterm zone="tutorial-fk">
     <primary>referential integrity</primary>
    </indexterm>
+  &pgnotice;
 
    <para>
     Recall the <classname>weather</classname> and
@@ -143,6 +146,7 @@ DETAIL:  Key (city)=(Berkeley) is not present in table "cities".
    <indexterm zone="tutorial-transactions">
     <primary>transaction</primary>
    </indexterm>
+  &pgnotice;
 
    <para>
     <firstterm>Transactions</> are a fundamental concept of all database
@@ -323,6 +327,7 @@ COMMIT;
    <indexterm zone="tutorial-window">
     <primary>window function</primary>
    </indexterm>
+  &pgnotice;
 
    <para>
     A <firstterm>window function</> performs a calculation across a set of
@@ -567,6 +572,7 @@ SELECT sum(salary) OVER w, avg(salary) OVER w
    <indexterm zone="tutorial-inheritance">
     <primary>inheritance</primary>
    </indexterm>
+  &pgnotice;
 
    <para>
     Inheritance is a concept from object-oriented databases.  It opens
@@ -699,6 +705,7 @@ SELECT name, altitude
 
   <sect1 id="tutorial-conclusion">
    <title>Conclusion</title>
+  &pgnotice;
 
    <para>
     <productname>PostgreSQL</productname> has many features not
diff --git a/doc/src/sgml/arch-dev.sgmlin b/doc/src/sgml/arch-dev.sgmlin
index b656f9b..c2bcca9 100644
--- a/doc/src/sgml/arch-dev.sgmlin
+++ b/doc/src/sgml/arch-dev.sgmlin
@@ -12,6 +12,7 @@
     of O.Univ.Prof.Dr. Georg Gottlob and Univ.Ass. Mag. Katrin Seyr.
    </para>
   </note>
+  &pgnotice;
 
   <para>
    This chapter gives an overview of the internal structure of the
@@ -28,6 +29,7 @@
 
   <sect1 id="query-path">
    <title>The Path of a Query</title>
+  &pgnotice;
 
    <para>
     Here we give a short overview of the stages a query has to pass in
@@ -115,6 +117,7 @@
 
   <sect1 id="connect-estab">
    <title>How Connections are Established</title>
+  &pgnotice;
 
    <para>
     <productname>PostgreSQL</productname> is implemented using a
@@ -154,6 +157,7 @@
 
   <sect1 id="parser-stage">
    <title>The Parser Stage</title>
+  &pgnotice;
 
    <para>
     The <firstterm>parser stage</firstterm> consists of two parts:
@@ -178,6 +182,7 @@
 
    <sect2>
     <title>Parser</title>
+  &pgnotice;
 
     <para>
      The parser has to check the query string (which arrives as plain
@@ -241,6 +246,7 @@
 
    <sect2>
      <title>Transformation Process</title>
+  &pgnotice;
 
     <para>
      The parser stage creates a parse tree using only fixed rules about
@@ -283,6 +289,7 @@
 
   <sect1 id="rule-system">
    <title>The <productname>PostgreSQL</productname> Rule System</title>
+  &pgnotice;
 
    <para>
     <productname>PostgreSQL</productname> supports a powerful
@@ -328,6 +335,7 @@
 
   <sect1 id="planner-optimizer">
    <title>Planner/Optimizer</title>
+  &pgnotice;
 
    <para>
     The task of the <firstterm>planner/optimizer</firstterm> is to
@@ -365,6 +373,7 @@
 
    <sect2>
     <title>Generating Possible Plans</title>
+  &pgnotice;
 
     <para>
      The planner/optimizer starts by generating plans for scanning each
@@ -477,6 +486,7 @@
 
   <sect1 id="executor">
    <title>Executor</title>
+  &pgnotice;
 
    <para>
     The <firstterm>executor</firstterm> takes the plan created by the
diff --git a/doc/src/sgml/array.sgmlin b/doc/src/sgml/array.sgmlin
index bfc373a..d5617b6 100644
--- a/doc/src/sgml/array.sgmlin
+++ b/doc/src/sgml/array.sgmlin
@@ -6,6 +6,7 @@
  <indexterm>
   <primary>array</primary>
  </indexterm>
+  &pgnotice;
 
  <para>
   <productname>PostgreSQL</productname> allows columns of a table to be
@@ -22,6 +23,7 @@
    <primary>array</primary>
    <secondary>declaration</secondary>
   </indexterm>
+  &pgnotice;
 
  <para>
   To illustrate the use of array types, we create this table:
@@ -92,6 +94,7 @@ CREATE TABLE tictactoe (
    <primary>array</primary>
    <secondary>constant</secondary>
   </indexterm>
+  &pgnotice;
 
   <para>
    To write an array value as a literal constant, enclose the element
@@ -204,6 +207,7 @@ INSERT INTO sal_emp
    <primary>array</primary>
    <secondary>accessing</secondary>
   </indexterm>
+  &pgnotice;
 
  <para>
   Now, we can run some queries on the table.
@@ -348,6 +352,7 @@ SELECT array_length(schedule, 1) FROM sal_emp WHERE name = 'Carol';
    <primary>array</primary>
    <secondary>modifying</secondary>
   </indexterm>
+  &pgnotice;
 
  <para>
   An array value can be replaced completely:
@@ -527,6 +532,7 @@ SELECT array_cat(ARRAY[5,6], ARRAY[[1,2],[3,4]]);
    <primary>array</primary>
    <secondary>searching</secondary>
   </indexterm>
+  &pgnotice;
 
  <para>
   To search for a value in an array, each value must be checked.
@@ -591,6 +597,7 @@ SELECT * FROM
    <primary>array</primary>
    <secondary>I/O</secondary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The external text representation of an array value consists of items that
diff --git a/doc/src/sgml/backup.sgmlin b/doc/src/sgml/backup.sgmlin
index e99d9dc..3767316 100644
--- a/doc/src/sgml/backup.sgmlin
+++ b/doc/src/sgml/backup.sgmlin
@@ -4,6 +4,7 @@
  <title>Backup and Restore</title>
 
  <indexterm zone="backup"><primary>backup</></>
+  &pgnotice;
 
  <para>
   As with everything that contains valuable data, <productname>PostgreSQL</>
@@ -26,6 +27,7 @@
 
  <sect1 id="backup-dump">
   <title><acronym>SQL</> Dump</title>
+  &pgnotice;
 
   <para>
    The idea behind this dump method is to generate a text file with SQL
@@ -104,6 +106,7 @@ pg_dump <replaceable class="parameter">dbname</replaceable> &gt; <replaceable cl
 
   <sect2 id="backup-dump-restore">
    <title>Restoring the dump</title>
+  &pgnotice;
 
    <para>
     The text files created by <application>pg_dump</> are intended to
@@ -189,6 +192,7 @@ pg_dump -h <replaceable>host1</> <replaceable>dbname</> | psql -h <replaceable>h
 
   <sect2 id="backup-dump-all">
    <title>Using <application>pg_dumpall</></title>
+  &pgnotice;
 
    <para>
     <application>pg_dump</> dumps only a single database at a time,
@@ -226,6 +230,7 @@ psql -f <replaceable class="parameter">infile</replaceable> postgres
 
   <sect2 id="backup-dump-large">
    <title>Handling large databases</title>
+  &pgnotice;
 
    <para>
     Some operating systems have maximum file size limits that cause
@@ -315,6 +320,7 @@ pg_restore -d <replaceable class="parameter">dbname</replaceable> <replaceable c
 
  <sect1 id="backup-file">
   <title>File System Level Backup</title>
+  &pgnotice;
 
   <para>
    An alternative backup strategy is to directly copy the files that
@@ -439,6 +445,7 @@ tar -cf backup.tar /usr/local/pgsql/data
   <indexterm zone="backup">
    <primary>PITR</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    At all times, <productname>PostgreSQL</> maintains a
@@ -526,6 +533,7 @@ tar -cf backup.tar /usr/local/pgsql/data
 
   <sect2 id="backup-archiving-wal">
    <title>Setting up WAL archiving</title>
+  &pgnotice;
 
    <para>
     In an abstract sense, a running <productname>PostgreSQL</> system
@@ -719,6 +727,7 @@ archive_command = 'test ! -f /mnt/server/archivedir/%f &amp;&amp; cp %p /mnt/ser
 
   <sect2 id="backup-base-backup">
    <title>Making a Base Backup</title>
+  &pgnotice;
 
    <para>
     The procedure for making a base backup is relatively simple:
@@ -923,6 +932,7 @@ SELECT pg_stop_backup();
 
   <sect2 id="backup-pitr-recovery">
    <title>Recovering using a Continuous Archive Backup</title>
+  &pgnotice;
 
    <para>
     Okay, the worst has happened and you need to recover from your backup.
@@ -1111,6 +1121,7 @@ restore_command = 'cp /mnt/server/archivedir/%f %p'
   <indexterm zone="backup">
    <primary>timelines</primary>
   </indexterm>
+  &pgnotice;
 
    <para>
     The ability to restore the database to a previous point in time creates
@@ -1175,6 +1186,7 @@ restore_command = 'cp /mnt/server/archivedir/%f %p'
 
   <sect2 id="backup-tips">
    <title>Tips and Examples</title>
+  &pgnotice;
 
    <para>
     Some tips for configuring continuous archiving are given here.
@@ -1182,6 +1194,7 @@ restore_command = 'cp /mnt/server/archivedir/%f %p'
 
     <sect3 id="backup-standalone">
      <title>Standalone hot backups</title>
+  &pgnotice;
 
      <para>
       It is possible to use <productname>PostgreSQL</>'s backup facilities to
@@ -1245,6 +1258,7 @@ restore_command = 'gunzip &lt; /mnt/server/archivedir/%f | pg_decompresslog - %p
 
     <sect3 id="backup-scripts">
      <title><varname>archive_command</varname> scripts</title>
+  &pgnotice;
 
      <para>
       Many people choose to use scripts to define their
@@ -1294,6 +1308,7 @@ archive_command = 'local_backup_script.sh'
 
   <sect2 id="continuous-archiving-caveats">
    <title>Caveats</title>
+  &pgnotice;
 
    <para>
     At this writing, there are several limitations of the continuous archiving
@@ -1375,6 +1390,7 @@ archive_command = 'local_backup_script.sh'
    <primary>version</primary>
    <secondary>compatibility</secondary>
   </indexterm>
+  &pgnotice;
 
   <para>
    This section discusses how to migrate your database data from one
@@ -1471,6 +1487,7 @@ archive_command = 'local_backup_script.sh'
 
   <sect2 id="migration-methods-pgdump">
    <title>Migrating data via <application>pg_dump</></title>
+  &pgnotice;
 
   <para>
    To dump data from one major version of <productname>PostgreSQL</> and
@@ -1551,6 +1568,7 @@ psql -f backup postgres
 
   <sect2 id="migration-methods-other">
    <title>Other data migration methods</title>
+  &pgnotice;
 
   <para>
    The <filename>contrib</> program
diff --git a/doc/src/sgml/basenam.sgmlin b/doc/src/sgml/basenam.sgmlin
index a755887..c81222f 100644
--- a/doc/src/sgml/basenam.sgmlin
+++ b/doc/src/sgml/basenam.sgmlin
@@ -28,6 +28,8 @@
   <title>Tutorial</title>
 
   <partintro>
+  &pgnotice;
+
    <para>
     Welcome to the <productname>PostgreSQL</productname> Tutorial.  The
     following few chapters are intended to give a simple introduction
diff --git a/doc/src/sgml/biblio.sgmlin b/doc/src/sgml/biblio.sgmlin
index 859b888..47ce658 100644
--- a/doc/src/sgml/biblio.sgmlin
+++ b/doc/src/sgml/biblio.sgmlin
@@ -7,6 +7,7 @@
    Selected references and readings for <acronym>SQL</acronym>
    and <productname>PostgreSQL</productname>.
   </para>
+  &pgnotice;
 
   <para>
    Some white papers and technical reports from the original
diff --git a/doc/src/sgml/btree-gin.sgmlin b/doc/src/sgml/btree-gin.sgmlin
index eb111bb..323f072 100644
--- a/doc/src/sgml/btree-gin.sgmlin
+++ b/doc/src/sgml/btree-gin.sgmlin
@@ -6,6 +6,7 @@
  <indexterm zone="btree-gin">
   <primary>btree_gin</primary>
  </indexterm>
+  &pgnotice;
 
  <para>
   <filename>btree_gin</> provides sample GIN operator classes that
@@ -45,6 +46,7 @@ SELECT * FROM test WHERE a &lt; 10;
 
  <sect2>
   <title>Authors</title>
+  &pgnotice;
 
   <para>
    Teodor Sigaev (<email>te...@st...</email>) and
diff --git a/doc/src/sgml/btree-gist.sgmlin b/doc/src/sgml/btree-gist.sgmlin
index 1d0a1e8..3782ce5 100644
--- a/doc/src/sgml/btree-gist.sgmlin
+++ b/doc/src/sgml/btree-gist.sgmlin
@@ -6,6 +6,7 @@
  <indexterm zone="btree-gist">
   <primary>btree_gist</primary>
  </indexterm>
+  &pgnotice;
 
  <para>
   <filename>btree_gist</> provides sample GiST operator classes that
@@ -42,6 +43,7 @@ SELECT * FROM test WHERE a &lt; 10;
 
  <sect2>
   <title>Authors</title>
+  &pgnotice;
 
   <para>
    Teodor Sigaev (<email>te...@st...</email>) ,
diff --git a/doc/src/sgml/catalogs.sgmlin b/doc/src/sgml/catalogs.sgmlin
index 6825bbc..3e94841 100644
--- a/doc/src/sgml/catalogs.sgmlin
+++ b/doc/src/sgml/catalogs.sgmlin
@@ -5,6 +5,7 @@
 
 <chapter id="catalogs">
  <title>System Catalogs</title>
+  &pgnotice;
 
   <para>
    The system catalogs are the place where a relational database
@@ -23,6 +24,7 @@
 
  <sect1 id="catalogs-overview">
   <title>Overview</title>
+  &pgnotice;
 
   <para>
    <xref linkend="catalog-table"> lists the system catalogs.
@@ -279,6 +281,7 @@
   <indexterm zone="catalog-pg-aggregate">
    <primary>pg_aggregate</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_aggregate</structname> stores information about
@@ -369,6 +372,7 @@
   <indexterm zone="catalog-pg-am">
    <primary>pg_am</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_am</structname> stores information about index
@@ -589,6 +593,7 @@
   <indexterm zone="catalog-pg-amop">
    <primary>pg_amop</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_amop</structname> stores information about
@@ -677,6 +682,7 @@
   <indexterm zone="catalog-pg-amproc">
    <primary>pg_amproc</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_amproc</structname> stores information about
@@ -758,6 +764,7 @@
   <indexterm zone="catalog-pg-attrdef">
    <primary>pg_attrdef</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_attrdef</structname> stores column default values.  The main information
@@ -829,6 +836,7 @@
   <indexterm zone="catalog-pg-attribute">
    <primary>pg_attribute</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_attribute</structname> stores information about
@@ -1075,6 +1083,7 @@
   <indexterm zone="catalog-pg-authid">
    <primary>pg_authid</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_authid</structname> contains information about
@@ -1208,6 +1217,7 @@
   <indexterm zone="catalog-pg-auth-members">
    <primary>pg_auth_members</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_auth_members</structname> shows the membership
@@ -1277,6 +1287,7 @@
   <indexterm zone="catalog-pg-cast">
    <primary>pg_cast</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_cast</structname> stores data type conversion
@@ -1399,6 +1410,7 @@
   <indexterm zone="catalog-pg-class">
    <primary>pg_class</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_class</structname> catalogs tables and most
@@ -1715,6 +1727,7 @@
   <indexterm zone="catalog-pg-constraint">
    <primary>pg_constraint</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_constraint</structname> stores check, primary
@@ -1975,6 +1988,7 @@
   <indexterm zone="catalog-pg-conversion">
    <primary>pg_conversion</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_conversion</structname> describes the
@@ -2060,6 +2074,7 @@
   <indexterm zone="catalog-pg-database">
    <primary>pg_database</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_database</structname> stores information about
@@ -2219,6 +2234,7 @@
   <indexterm zone="catalog-pg-db-role-setting">
    <primary>pg_db_role_setting</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_db_role_setting</structname> records the default
@@ -2279,6 +2295,7 @@
   <indexterm zone="catalog-pg-default-acl">
    <primary>pg_default_acl</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_default_acl</> stores initial
@@ -2366,6 +2383,7 @@
   <indexterm zone="catalog-pg-depend">
    <primary>pg_depend</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_depend</structname> records the dependency
@@ -2540,6 +2558,7 @@
   <indexterm zone="catalog-pg-description">
    <primary>pg_description</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_description</> stores optional descriptions
@@ -2615,6 +2634,7 @@
   <indexterm zone="catalog-pg-enum">
    <primary>pg_enum</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The <structname>pg_enum</structname> catalog contains entries
@@ -2665,6 +2685,7 @@
   <indexterm zone="catalog-pg-foreign-data-wrapper">
    <primary>pg_foreign_data_wrapper</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_foreign_data_wrapper</structname> stores
@@ -2746,6 +2767,7 @@
   <indexterm zone="catalog-pg-foreign-server">
    <primary>pg_foreign_server</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_foreign_server</structname> stores
@@ -2835,6 +2857,7 @@
   <indexterm zone="catalog-pg-index">
    <primary>pg_index</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_index</structname> contains part of the information
@@ -3016,6 +3039,7 @@
   <indexterm zone="catalog-pg-inherits">
    <primary>pg_inherits</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_inherits</> records information about
@@ -3079,6 +3103,7 @@
   <indexterm zone="catalog-pg-language">
    <primary>pg_language</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_language</structname> registers
@@ -3199,6 +3224,7 @@
   <indexterm zone="catalog-pg-largeobject">
    <primary>pg_largeobject</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_largeobject</structname> holds the data making up
@@ -3279,6 +3305,7 @@
   <indexterm zone="catalog-pg-largeobject-metadata">
    <primary>pg_largeobject_metadata</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_largeobject_metadata</structname>
@@ -3331,6 +3358,7 @@
   <indexterm zone="catalog-pg-namespace">
    <primary>pg_namespace</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_namespace</> stores namespaces.
@@ -3391,6 +3419,7 @@
   <indexterm zone="catalog-pg-opclass">
    <primary>pg_opclass</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_opclass</structname> defines
@@ -3498,6 +3527,7 @@
   <indexterm zone="catalog-pg-operator">
    <primary>pg_operator</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_operator</> stores information about operators.
@@ -3639,6 +3669,7 @@
   <indexterm zone="catalog-pg-opfamily">
    <primary>pg_opfamily</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_opfamily</structname> defines operator families.
@@ -3719,6 +3750,7 @@
   <indexterm zone="catalog-pg-pltemplate">
    <primary>pg_pltemplate</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_pltemplate</structname> stores
@@ -3825,6 +3857,7 @@
   <indexterm zone="catalog-pg-proc">
    <primary>pg_proc</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_proc</> stores information about functions (or procedures).
@@ -4121,6 +4154,7 @@
   <indexterm zone="catalog-pg-rewrite">
    <primary>pg_rewrite</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_rewrite</structname> stores rewrite rules for tables and views.
@@ -4235,6 +4269,7 @@
   <indexterm zone="catalog-pg-shdepend">
    <primary>pg_shdepend</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_shdepend</structname> records the
@@ -4388,6 +4423,7 @@
   <indexterm zone="catalog-pg-shdescription">
    <primary>pg_shdescription</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_shdescription</structname> stores optional
@@ -4456,6 +4492,7 @@
   <indexterm zone="catalog-pg-statistic">
    <primary>pg_statistic</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_statistic</structname> stores
@@ -4636,6 +4673,7 @@
   <indexterm zone="catalog-pg-tablespace">
    <primary>pg_tablespace</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_tablespace</structname> stores information
@@ -4717,6 +4755,7 @@
   <indexterm zone="catalog-pg-trigger">
    <primary>pg_trigger</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_trigger</structname> stores triggers on tables.
@@ -4893,6 +4932,7 @@
   <indexterm zone="catalog-pg-ts-config">
    <primary>pg_ts_config</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The <structname>pg_ts_config</structname> catalog contains entries
@@ -4964,6 +5004,7 @@
   <indexterm zone="catalog-pg-ts-config-map">
    <primary>pg_ts_config_map</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The <structname>pg_ts_config_map</structname> catalog contains entries
@@ -5031,6 +5072,7 @@
   <indexterm zone="catalog-pg-ts-dict">
    <primary>pg_ts_dict</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The <structname>pg_ts_dict</structname> catalog contains entries
@@ -5110,6 +5152,7 @@
   <indexterm zone="catalog-pg-ts-parser">
    <primary>pg_ts_parser</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The <structname>pg_ts_parser</structname> catalog contains entries
@@ -5200,6 +5243,7 @@
   <indexterm zone="catalog-pg-ts-template">
    <primary>pg_ts_template</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The <structname>pg_ts_template</structname> catalog contains entries
@@ -5269,6 +5313,7 @@
   <indexterm zone="catalog-pg-type">
    <primary>pg_type</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_type</structname> stores information about data
@@ -5746,6 +5791,7 @@
   <indexterm zone="catalog-pg-user-mapping">
    <primary>pg_user_mapping</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The catalog <structname>pg_user_mapping</structname> stores
@@ -5801,6 +5847,7 @@
 
  <sect1 id="views-overview">
   <title>System Views</title>
+  &pgnotice;
 
   <para>
    In addition to the system catalogs, <productname>PostgreSQL</productname>
@@ -5938,6 +5985,7 @@
   <indexterm zone="view-pg-cursors">
    <primary>pg_cursors</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The <structname>pg_cursors</structname> view lists the cursors that
@@ -6058,6 +6106,7 @@
   <indexterm zone="view-pg-group">
    <primary>pg_group</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The view <structname>pg_group</structname> exists for backwards
@@ -6114,6 +6163,7 @@
   <indexterm zone="view-pg-indexes">
    <primary>pg_indexes</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The view <structname>pg_indexes</structname> provides access to
@@ -6176,6 +6226,7 @@
   <indexterm zone="view-pg-locks">
    <primary>pg_locks</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The view <structname>pg_locks</structname> provides access to
@@ -6438,6 +6489,7 @@
   <indexterm zone="view-pg-prepared-statements">
    <primary>pg_prepared_statements</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The <structname>pg_prepared_statements</structname> view displays
@@ -6526,6 +6578,7 @@
   <indexterm zone="view-pg-prepared-xacts">
    <primary>pg_prepared_xacts</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The view <structname>pg_prepared_xacts</structname> displays
@@ -6614,6 +6667,7 @@
   <indexterm zone="view-pg-roles">
    <primary>pg_roles</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The view <structname>pg_roles</structname> provides access to
@@ -6741,6 +6795,7 @@
   <indexterm zone="view-pg-rules">
    <primary>pg_rules</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The view <structname>pg_rules</structname> provides access to
@@ -6801,6 +6856,7 @@
   <indexterm zone="view-pg-settings">
    <primary>pg_settings</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The view <structname>pg_settings</structname> provides access to
@@ -6943,6 +6999,7 @@
   <indexterm zone="view-pg-shadow">
    <primary>pg_shadow</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The view <structname>pg_shadow</structname> exists for backwards
@@ -7047,6 +7104,7 @@
   <indexterm zone="view-pg-stats">
    <primary>pg_stats</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The view <structname>pg_stats</structname> provides access to
@@ -7211,6 +7269,7 @@
   <indexterm zone="view-pg-tables">
    <primary>pg_tables</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The view <structname>pg_tables</structname> provides access to
@@ -7284,6 +7343,7 @@
   <indexterm zone="view-pg-timezone-abbrevs">
    <primary>pg_timezone_abbrevs</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The view <structname>pg_timezone_abbrevs</structname> provides a list
@@ -7331,6 +7391,7 @@
   <indexterm zone="view-pg-timezone-names">
    <primary>pg_timezone_names</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The view <structname>pg_timezone_names</structname> provides a list
@@ -7388,6 +7449,7 @@
   <indexterm zone="view-pg-user">
    <primary>pg_user</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The view <structname>pg_user</structname> provides access to
@@ -7471,6 +7533,7 @@
   <indexterm zone="view-pg-user-mappings">
    <primary>pg_user_mappings</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The view <structname>pg_user_mappings</structname> provides access
@@ -7556,6 +7619,7 @@
   <indexterm zone="view-pg-views">
    <primary>pg_views</primary>
   </indexterm>
+  &pgnotice;
 
   <para>
    The view <structname>pg_views</structname> provides access to
diff --git a/doc/src/sgml/chkpass.sgmlin b/doc/src/sgml/chkpass.sgmlin
index 865300f..517f906 100644
--- a/doc/src/sgml/chkpass.sgmlin
+++ b/doc/src/sgml/chkpass.sgmlin
@@ -14,6 +14,7 @@
   and is always stored encrypted.  To compare, simply compare against a clear
   text password and the comparison function will encrypt it before comparing.
  </para>
+  &pgnotice;
 
  <para>
   There are provisions in the code to report an error if the password is
@@ -86,6 +87,7 @@ test=# select p = 'goodbye' from test;
 
  <sect2>
   <title>Author</title>
+  &pgnotice;
 
   <para>
    D'Arcy J.M. Cain (<email>da...@dr...</email>)
diff --git a/doc/src/sgml/citext.sgmlin b/doc/src/sgml/citext.sgmlin
index 23d53a6..fbd461a 100644
--- a/doc/src/sgml/citext.sgmlin
+++ b/doc/src/sgml/citext.sgmlin
@@ -6,6 +6,7 @@
  <indexterm zone="citext">
   <primary>citext</primary>
  </indexterm>
+  &pgnotice;
 
  <para>
   The <filename>citext</> module provides a case-insensitive
@@ -16,6 +17,7 @@
 
  <sect2>
   <title>Rationale</title>
+  &pgnotice;
 
   <para>
    The standard approach to doing case-insensitive matches
@@ -70,6 +72,7 @@ SELECT * FROM tab WHERE lower(col) = LOWER(?);
 
  <sect2>
   <title>How to Use It</title>
+  &pgnotice;
 
   <para>
    Here's a simple example of usage:
@@ -97,6 +100,8 @@ SELECT * FROM users WHERE nick = 'Larry';
 
  <sect2>
   <title>String Comparison Behavior</title>
+  &pgnotice;
+
   <para>
    In order to emulate a case-insensitive collation as closely as possible,
    there are <type>citext</>-specific versions of a number of the comparison
@@ -167,6 +172,8 @@ SELECT * FROM users WHERE nick = 'Larry';
 
    <itemizedlist>
     <listitem>
+  &pgnotice;
+
      <para>
       <type>citext</>'s behavior depends on
       the <literal>LC_CTYPE</> setting of your database. How it compares
@@ -219,6 +226,7 @@ SELECT * FROM users WHERE nick = 'Larry';
 
  <sect2>
   <title>Author</title>
+  &pgnotice;
 
   <para>
    David E. Wheeler <email>da...@ki...</email>
diff --git a/doc/src/sgml/config.sgmlin b/doc/src/sgml/config.sgmlin
index 1b8e5a5..f7f198e 100644
--- a/doc/src/sgml/config.sgmlin
+++ b/doc/src/sgml/config.sgmlin
@@ -7,6 +7,7 @@
    <primary>configuration</primary>
    <secondary>of the server</secondary>
   </indexterm>
+  &pgnotice;
 
   <para>
    There are many configuration parameters that affect the behavior of
@@ -17,6 +18,7 @@
 
   <sect1 id="config-setting">
    <title>Setting Parameters</title>
+  &pgnotice;
 
    <para>
     All parameter names are case-insensitive. Every parameter takes a
@@ -178,6 +180,7 @@ SET ENABLE_SEQSCAN TO OFF;
 
    <sect1 id="runtime-config-file-locations">
     <title>File Locations</title>
+  &pgnotice;
 
      <para>
       In addition to the <filename>postgresql.conf</filename> file
@@ -319,6 +322,8 @@ SET ENABLE_SEQSCAN TO OFF;
        <primary><varname>listen_addresses</> configuration parameter</primary>
       </indexterm>
       <listitem>
+  &pgnotice;
+
        <para>
          Specifies the TCP/IP address(es) on which the server is
          to listen for connections from client applications.
@@ -622,6 +627,8 @@ SET ENABLE_SEQSCAN TO OFF;
       </indexterm>
 
       <listitem>
+  &pgnotice;
+
        <para>
         Maximum time to complete client authentication, in seconds. If a
         would-be client has not completed the authentication protocol in
@@ -823,6 +830,8 @@ SET ENABLE_SEQSCAN TO OFF;
        <primary><varname>shared_buffers</> configuration parameter</primary>
       </indexterm>
       <listitem>
+  &pgnotice;
+
        <para>
         Sets the amount of memory the database server uses for shared
         memory buffers.  The default is typically 32 megabytes
@@ -1032,6 +1041,8 @@ SET ENABLE_SEQSCAN TO OFF;
        <primary><varname>max_files_per_process</> configuration parameter</primary>
       </indexterm>
       <listitem>
+  &pgnotice;
+
        <para>
         Sets the maximum number of simultaneously open files allowed to each
         server subprocess. The default is one thousand files. If the kernel is enforcing
@@ -1110,6 +1121,7 @@ SET ENABLE_SEQSCAN TO OFF;
 
     <sect2 id="runtime-config-resource-vacuum-cost">
      <title>Cost-Based Vacuum Delay</title>
+  &pgnotice;
 
      <para>
       During the execution of <xref linkend="sql-vacuum">
@@ -1247,6 +1259,7 @@ SET ENABLE_SEQSCAN TO OFF;
 
     <sect2 id="runtime-config-resource-background-writer">
      <title>Background Writer</title>
+  &pgnotice;
 
      <para>
       There is a separate server
@@ -1349,6 +1362,8 @@ SET ENABLE_SEQSCAN TO OFF;
         <primary><varname>effective_io_concurrency</> configuration parameter</primary>
        </indexterm>
        <listitem>
+  &pgnotice;
+
         <para>
          Sets the number of concurrent disk I/O operations that
          <productname>PostgreSQL</> expects can be executed
@@ -1390,6 +1405,7 @@ SET ENABLE_SEQSCAN TO OFF;
 
    <sect1 id="runtime-config-wal">
     <title>Write Ahead Log</title>
+  &pgnotice;
 
    <para>
     See also <xref linkend="wal-configuration"> for details on WAL
@@ -1406,6 +1422,8 @@ SET ENABLE_SEQSCAN TO OFF;
        <primary><varname>wal_level</> configuration parameter</primary>
       </indexterm>
       <listitem>
+  &pgnotice;
+
        <para>
         <varname>wal_level</> determines how much information is written
         to the WAL. The default value is <literal>minimal</>, which writes
@@ -1726,6 +1744,8 @@ SET ENABLE_SEQSCAN TO OFF;
        <primary><varname>checkpoint_segments</> configuration parameter</primary>
       </indexterm>
       <listitem>
+  &pgnotice;
+
        <para>
         Maximum number of log file segments between automatic WAL
         checkpoints (each segment is normally 16 megabytes). The default
@@ -1800,6 +1820,8 @@ SET ENABLE_SEQSCAN TO OFF;
        <primary><varname>archive_mode</> configuration parameter</primary>
       </indexterm>
       <listitem>
+  &pgnotice;
+
        <para>
         When <varname>archive_mode</> is enabled, completed WAL segments
         are sent to archive storage by setting
@@ -1885,6 +1907,7 @@ SET ENABLE_SEQSCAN TO OFF;
 
     <sect2 id="runtime-config-replication">
      <title>Streaming Replication</title>
+  &pgnotice;
 
      <para>
       These settings control the behavior of the built-in
@@ -1993,6 +2016,7 @@ SET ENABLE_SEQSCAN TO OFF;
 
     <sect2 id="runtime-config-standby">
     <title>Standby Servers</title>
+  &pgnotice;
 
      <para>
       These settings control the behavior of a standby server that is
@@ -2087,6 +2111,7 @@ SET ENABLE_SEQSCAN TO OFF;
 
     <sect2 id="runtime-config-query-enable">
      <title>Planner Method Configuration</title>
+  &pgnotice;
 
       <para>
        These configuration parameters provide a crude method of
@@ -2262,6 +2287,7 @@ SET ENABLE_SEQSCAN TO OFF;
      </sect2>
      <sect2 id="runtime-config-query-constants">
      <title>Planner Cost Constants</title>
+  &pgnotice;
 
     <para>
      The <firstterm>cost</> variables described in this section are measured
@@ -2414,6 +2440,7 @@ SET ENABLE_SEQSCAN TO OFF;
     </sect2>
      <sect2 id="runtime-config-query-geqo">
      <title>Genetic Query Optimizer</title>
+  &pgnotice;
 
      <para>
       The genetic query optimizer (GEQO) is an algorithm that does query
@@ -2561,6 +2588,7 @@ SET ENABLE_SEQSCAN TO OFF;
     </sect2>
      <sect2 id="runtime-config-query-other">
      <title>Other Planner Options</title>
+  &pgnotice;
 
      <variablelist>
 
@@ -2725,6 +2753,7 @@ SELECT * FROM parent WHERE key = 2400;
     <indexterm zone="runtime-config-logging">
      <primary>server log</primary>
     </indexterm>
+  &pgnotice;
 
     <sect2 id="runtime-config-logging-where">
      <title>Where To Log</title>
@@ -2732,6 +2761,7 @@ SELECT * FROM parent WHERE key = 2400;
      <indexterm zone="runtime-config-logging-where">
       <primary>where to log</primary>
      </indexterm>
+  &pgnotice;
 
      <variablelist>
 
@@ -3029,6 +3059,7 @@ local0.*    /var/log/postgresql
     </sect2>
      <sect2 id="runtime-config-logging-when">
      <title>When To Log</title>
+  &pgnotice;
 
      <variablelist>
 
@@ -3234,6 +3265,7 @@ local0.*    /var/log/postgresql
     </sect2>
      <sect2 id="runtime-config-logging-what">
      <title>What To Log</title>
+  &pgnotice;
 
      <variablelist>
 
@@ -3686,6 +3718,7 @@ FROM pg_stat_activity;
     </sect2>
      <sect2 id="runtime-config-logging-csvlog">
      <title>Using CSV-Format Log Output</title>
+  &pgnotice;
 
        <para>
         Including <literal>csvlog</> in the <varname>log_destination</> list
@@ -3812,9 +3845,11 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
 
    <sect1 id="runtime-config-statistics">
     <title>Run-Time Statistics</title>
+  &pgnotice;
 
     <sect2 id="runtime-config-statistics-collector">
      <title>Query and Index Statistics Collector</title>
+  &pgnotice;
 
      <para>
       These parameters control server-wide statistics collection features.
@@ -3939,6 +3974,9 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
 
     <sect2 id="runtime-config-statistics-monitor">
      <title>Statistics Monitoring</title>
+  &pgnotice;
+
+
      <variablelist>
 
      <varlistentry>
@@ -3979,6 +4017,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
 
    <sect1 id="runtime-config-autovacuum">
     <title>Automatic Vacuuming</title>
+  &pgnotice;
 
     <indexterm>
      <primary>autovacuum</primary>
@@ -4215,9 +4254,12 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
 
    <sect1 id="runtime-config-client">
     <title>Client Connection Defaults</title>
+  &pgnotice;
 
     <sect2 id="runtime-config-client-statement">
      <title>Statement Behavior</title>
+  &pgnotice;
+
      <variablelist>
 
      <varlistentry id="guc-search-path" xreflabel="search_path">
@@ -4605,6 +4647,7 @@ SET XML OPTION { DOCUMENT | CONTENT };
     </sect2>
      <sect2 id="runtime-config-client-format">
      <title>Locale and Formatting</title>
+  &pgnotice;
 
      <variablelist>
 
@@ -4851,6 +4894,7 @@ SET XML OPTION { DOCUMENT | CONTENT };
     </sect2>
      <sect2 id="runtime-config-client-other">
      <title>Other Defaults</title>
+  &pgnotice;
 
      <variablelist>
 
@@ -4982,6 +5026,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
 
    <sect1 id="runtime-config-locks">
     <title>Lock Management</title>
+  &pgnotice;
 
      <variablelist>
 
@@ -5071,9 +5116,11 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
 
    <sect1 id="runtime-config-compatible">
     <title>Version and Platform Compatibility</title>
+  &pgnotice;
 
     <sect2 id="runtime-config-compatible-version">
      <title>Previous PostgreSQL Versions</title>
+  &pgnotice;
 
      <variablelist>
 
@@ -5284,6 +5331,8 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
 
     <sect2 id="runtime-config-compatible-clients">
      <title>Platform and Client Compatibility</title>
+  &pgnotice;
+
      <variablelist>
 
      <varlistentry id="guc-transform-null-equals" xreflabel="transform_null_equals">
@@ -5339,6 +5388,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
 
    <sect1 id="runtime-config-preset">
     <title>Preset Options</title>
+  &pgnotice;
 
     <para>
      The following <quote>parameters</> are read-only, and are determined
@@ -5553,6 +5603,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
 
    <sect1 id="runtime-config-custom">
     <title>Customized Options</title>
+  &pgnotice;
 
     <para>
      This feature was designed to allow parameters not normally known to
@@ -5614,6 +5665,7 @@ plruby.use_strict = true        # generates error: unknown class name
 
    <sect1 id="runtime-config-developer">
     <title>Developer Options</title>
+  &pgnotice;
 
     <para>
      The following parameters are intended for work on the
@@ -5961,6 +6013,7 @@ LOG:  CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1)
   </sect1>
   <sect1 id="runtime-config-short">
    <title>Short Options</title>
+  &pgnotice;
 
    <para>
     For convenience there are also single letter command-line option
diff --git a/doc/src/sgml/contacts.sgmlin b/doc/src/sgml/contacts.sgmlin
index 6b15de3..038ebbc 100644
--- a/doc/src/sgml/contacts.sgmlin
+++ b/doc/src/sgml/contacts.sgmlin
@@ -1,9 +1,9 @@
 <!-- $PostgreSQL: pgsql/doc/src/sgml/contacts.sgml,v 1.9 2006/03/10 19:10:47 momjian Exp $ -->
 
+
 <appendix label="B" id="contacts">
 <title>Contacts</title>
-
-<!--
+%pgnotice;
 <para>
 Support for <productname>PostgreSQL</productname> comes primarily from
 this printed documentation, the web-based mailing list archives,
@@ -12,6 +12,7 @@ and the mailing lists themselves.
 
 <sect1 id="mailing-list">
 <title>Mailing Lists</title>
+%pgnotice;
 
 <para>
 Refer to the introduction in this manual or to the
@@ -22,5 +23,6 @@ for subscription information to the no-cost mailing lists.
 
 <sect1 id="people">
 <title>People</title>
--->
+%pgnotice;
+
 </appendix>
diff --git a/doc/src/sgml/contrib.sgmlin b/doc/src/sgml/contrib.sgmlin
index b801c40..d214df5 100644
--- a/doc/src/sgml/contrib.sgmlin
+++ b/doc/src/sgml/contrib.sgmlin
@@ -2,6 +2,7 @@
 
 <appendix id="contrib">
  <title>Additional Supplied Modules</title>
+&pgnotice;
 
  <para>
   This appendix contains information regarding the modules that
diff --git a/doc/src/sgml/cube.sgmlin b/doc/src/sgml/cube.sgmlin
index 5da1301..75ce194 100644
--- a/doc/src/sgml/cube.sgmlin
+++ b/doc/src/sgml/cube.sgmlin
@@ -6,6 +6,7 @@
  <indexterm zone="cube">
   <primary>cube</primary>
  </indexterm>
+&pgnotice;
 
  <para>
   This module implements a data type <type>cube</> for
@@ -14,6 +15,7 @@
 
  <sect2>
   <title>Syntax</title>
+&pgnotice;
 
   <para>
    <xref linkend="cube-repr-table"> shows the valid external
@@ -85,6 +87,7 @@
 
  <sect2>
   <title>Precision</title>
+&pgnotice;
 
   <para>
    Values are stored internally as 64-bit floating point numbers. This means
@@ -94,6 +97,7 @@
 
  <sect2>
   <title>Usage</title>
+&pgnotice;
 
   <para>
    The <filename>cube</> module includes a GiST index operator class for
@@ -313,6 +317,7 @@
 
  <sect2>
   <title>Defaults</title>
+&pgnotice;
 
   <para>
    I believe this union:
@@ -367,6 +372,7 @@ t
 
  <sect2>
   <title>Notes</title>
+&pgnotice;
 
   <para>
    For examples of usage, see the regression test <filename>sql/cube.sql</>.
@@ -381,6 +387,7 @@ t
 
  <sect2>
   <title>Credits</title>
+&pgnotice;
 
   <para>
    Original author: Gene Selkov, Jr. <email>sel...@mc...</email>,
diff --git a/doc/src/sgml/datatype.sgmlin b/doc/src/sgml/datatype.sgmlin
index 0e07cc3..ab6250d 100644
--- a/doc/src/sgml/datatype.sgmlin
+++ b/doc/src/sgml/datatype.sgmlin
@@ -3,6 +3,7 @@
  <chapter id="datatype">
   <title>Data Types</title>
 
+
   <indexterm zone="datatype">
    <primary>data type</primary>
   </indexterm>
@@ -11,7 +12,7 @@
    <primary>type</primary>
    <see>data type</see>
   </indexterm>
-
+&pgnotice;
   <para>
    <productname>PostgreSQL</productname> has a rich set of native data
    types available to users.  Users can add new types to
@@ -302,6 +303,7 @@
     <primary>data type</primary>
     <secondary>numeric</secondary>
    </indexterm>
+&pgnotice;
 
    <para>
     Numeric types consist of two-, four-, and eight-byte integers,
@@ -422,6 +424,7 @@
      <primary>int8</primary>
      <see>bigint</see>
     </indexterm>
+&pgnotice;
 
     <para>
      The types <type>smallint</type>, <type>integer</type>, and
@@ -474,6 +477,7 @@
      <primary>decimal</primary>
      <see>numeric</see>
     </indexterm>
+&pgnotice;
 
     <para>
      The type <type>numeric</type> can store numbers with up to 1000
@@ -607,6 +611,7 @@ NUMERIC
     <indexterm zone="datatype-float">
      <primary>floating point</primary>
     </indexterm>
+&pgnotice;
 
     <para>
      The data types <type>real</type> and <type>double
@@ -758,6 +763,7 @@ NUMERIC
      <primary>sequence</primary>
      <secondary>and serial type</secondary>
     </indexterm>
+&pgnotice;
 
     <para>
      The data types <type>serial</type> and <type>bigserial</type>
@@ -833,6 +839,7 @@ ALTER SEQUENCE <replaceable class="parameter">tablename</replaceable>_<replaceab
 
   <sect1 id="datatype-money">
    <title>Monetary Types</title>
+&pgnotice;
 
    <para>
     The <type>money</type> type stores a currency amount with a fixed
@@ -893,6 +900,7 @@ SELECT regexp_replace('52093.89'::money::text, '[$,]', '', 'g')::numeric;
 
   <sect1 id="datatype-character">
    <title>Character Types</title>
+&pgnotice;
 
    <indexterm zone="datatype-character">
     <primary>character string</primary>
diff --git a/doc/src/sgml/datetime.sgmlin b/doc/src/sgml/datetime.sgmlin
index d072118..8e75a51 100644
--- a/doc/src/sgml/datetime.sgmlin
+++ b/doc/src/sgml/datetime.sgmlin
@@ -2,7 +2,7 @@
 
  <appendix id="datetime-appendix">
   <title>Date/Time Support</title>
-
+  &pgnotice;
   <para>
    <productname>PostgreSQL</productname> uses an internal heuristic
    parser for all date/time input support. Dates and times are input as
@@ -22,7 +22,7 @@
 
   <sect1 id="datetime-input-rules">
    <title>Date/Time Input Interpretation</title>
-
+  &pgnotice;
    <para>
     The date/time type inputs are all decoded using the following procedure.
    </para>
@@ -178,7 +178,7 @@
 
   <sect1 id="datetime-keywords">
    <title>Date/Time Key Words</title>
-
+  &pgnotice;
    <para>
     <xref linkend="datetime-month-table"> shows the tokens that are
     recognized as names of months.
@@ -344,7 +344,7 @@
     <primary>time zone</primary>
     <secondary>input abbreviations</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     Since timezone abbreviations are not well standardized,
     <productname>PostgreSQL</productname> provides a means to customize
@@ -455,7 +455,7 @@
 
   <sect1 id="datetime-units-history">
   <title>History of Units</title>
-
+  &pgnotice;
   <para>
    The Julian calendar was introduced by Julius Caesar in 45 BC.
    It was in common use in the Western world
diff --git a/doc/src/sgml/dblink.sgmlin b/doc/src/sgml/dblink.sgmlin
index 3530fc1..2c3b9f1 100644
--- a/doc/src/sgml/dblink.sgmlin
+++ b/doc/src/sgml/dblink.sgmlin
@@ -6,7 +6,7 @@
  <indexterm zone="dblink">
   <primary>dblink</primary>
  </indexterm>
-
+  &pgnotice;
  <para>
   <filename>dblink</> is a module which supports connections to
   other <productname>PostgreSQL</> databases from within a database
diff --git a/doc/src/sgml/ddl.sgmlin b/doc/src/sgml/ddl.sgmlin
index 86cf6ec..c265a54 100644
--- a/doc/src/sgml/ddl.sgmlin
+++ b/doc/src/sgml/ddl.sgmlin
@@ -2,7 +2,7 @@
 
 <chapter id="ddl">
  <title>Data Definition</title>
-
+  &pgnotice;
  <para>
   This chapter covers how one creates the database structures that
   will hold one's data.  In a relational database, the raw data is
@@ -29,7 +29,7 @@
   <indexterm>
    <primary>column</primary>
   </indexterm>
-
+  &pgnotice;
   <para>
    A table in a relational database is much like a table on paper: It
    consists of rows and columns.  The number and order of the columns
@@ -173,7 +173,7 @@ DROP TABLE products;
   <indexterm zone="ddl-default">
    <primary>default value</primary>
   </indexterm>
-
+  &pgnotice;
   <para>
    A column can be assigned a default value.  When a new row is
    created and no values are specified for some of the columns, those
@@ -238,7 +238,7 @@ CREATE TABLE products (
   <indexterm zone="ddl-constraints">
    <primary>constraint</primary>
   </indexterm>
-
+  &pgnotice;
   <para>
    Data types are a way to limit the kind of data that can be stored
    in a table.  For many applications, however, the constraint they
@@ -269,7 +269,7 @@ CREATE TABLE products (
     <primary>constraint</primary>
     <secondary>check</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     A check constraint is the most generic constraint type.  It allows
     you to specify that the value in a certain column must satisfy a
@@ -415,7 +415,7 @@ CREATE TABLE products (
     <primary>constraint</primary>
     <secondary>NOT NULL</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     A not-null constraint simply specifies that a column must not
     assume the null value.  A syntax example:
@@ -493,7 +493,7 @@ CREATE TABLE products (
     <primary>constraint</primary>
     <secondary>unique</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     Unique constraints ensure that the data contained in a column or a
     group of columns is unique with respect to all the rows in the
@@ -580,7 +580,7 @@ CREATE TABLE products (
     <primary>constraint</primary>
     <secondary>primary key</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     Technically, a primary key constraint is simply a combination of a
     unique constraint and a not-null constraint.  So, the following
@@ -658,7 +658,7 @@ CREATE TABLE example (
    <indexterm>
     <primary>referential integrity</primary>
    </indexterm>
-
+  &pgnotice;
    <para>
     A foreign key constraint specifies that the values in a column (or
     a group of columns) must match the values appearing in some row
@@ -877,7 +877,7 @@ CREATE TABLE order_items (
     <primary>constraint</primary>
     <secondary>exclusion</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     Exclusion constraints ensure that if any two rows are compared on
     the specified columns or expressions using the specified operators,
@@ -905,7 +905,7 @@ CREATE TABLE circles (
 
  <sect1 id="ddl-system-columns">
   <title>System Columns</title>
-
+  &pgnotice;
   <para>
    Every table has several <firstterm>system columns</> that are
    implicitly defined by the system.  Therefore, these names cannot be
@@ -1108,7 +1108,7 @@ CREATE TABLE circles (
    <primary>table</primary>
    <secondary>modifying</secondary>
   </indexterm>
-
+  &pgnotice;
   <para>
    When you create a table and you realize that you made a mistake, or
    the requirements of the application change, you can drop the
@@ -1164,7 +1164,7 @@ CREATE TABLE circles (
     <primary>column</primary>
     <secondary>adding</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     To add a column, use a command like:
 <programlisting>
@@ -1208,7 +1208,7 @@ ALTER TABLE products ADD COLUMN description text CHECK (description &lt;&gt; '')
     <primary>column</primary>
     <secondary>removing</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     To remove a column, use a command like:
 <programlisting>
@@ -1235,7 +1235,7 @@ ALTER TABLE products DROP COLUMN description CASCADE;
     <primary>constraint</primary>
     <secondary>adding</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     To add a constraint, the table constraint syntax is used.  For example:
 <programlisting>
@@ -1263,7 +1263,7 @@ ALTER TABLE products ALTER COLUMN product_no SET NOT NULL;
     <primary>constraint</primary>
     <secondary>removing</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     To remove a constraint you need to know its name.  If you gave it
     a name then that's easy.  Otherwise the system assigned a
@@ -1304,7 +1304,7 @@ ALTER TABLE products ALTER COLUMN product_no DROP NOT NULL;
     <primary>default value</primary>
     <secondary>changing</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     To set a new default for a column, use a command like:
 <programlisting>
@@ -1333,7 +1333,7 @@ ALTER TABLE products ALTER COLUMN price DROP DEFAULT;
     <primary>column data type</primary>
     <secondary>changing</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     To convert a column to a different data type, use a command like:
 <programlisting>
@@ -1362,7 +1362,7 @@ ALTER TABLE products ALTER COLUMN price TYPE numeric(10,2);
     <primary>column</primary>
     <secondary>renaming</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     To rename a column:
 <programlisting>
@@ -1378,7 +1378,7 @@ ALTER TABLE products RENAME COLUMN product_no TO product_number;
     <primary>table</primary>
     <secondary>renaming</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     To rename a table:
 <programlisting>
@@ -1399,7 +1399,7 @@ ALTER TABLE products RENAME TO items;
    <primary>permission</primary>
    <see>privilege</see>
   </indexterm>
-
+  &pgnotice;
   <para>
    When you create a database object, you become its owner.  By
    default, only the owner of an object can do anything with the
@@ -1490,7 +1490,7 @@ REVOKE ALL ON accounts FROM PUBLIC;
   <indexterm zone="ddl-schemas">
    <primary>schema</primary>
   </indexterm>
-
+  &pgnotice;
   <para>
    A <productname>PostgreSQL</productname> database cluster
    contains one or more named databases.  Users and groups of users are
@@ -1559,7 +1559,7 @@ REVOKE ALL ON accounts FROM PUBLIC;
     <primary>schema</primary>
     <secondary>creating</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     To create a schema, use the <xref linkend="sql-createschema">
     command.  Give the schema a name
@@ -1655,7 +1655,7 @@ CREATE SCHEMA <replaceable>schemaname</replaceable> AUTHORIZATION <replaceable>u
     <primary>schema</primary>
     <secondary>public</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     In the previous sections we created tables without specifying any
     schema names.  By default such tables (and other objects) are
@@ -1686,7 +1686,7 @@ CREATE TABLE public.products ( ... );
     <primary>name</primary>
     <secondary>unqualified</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     Qualified names are tedious to write, and it's often best not to
     wire a particular schema name into applications anyway.  Therefore
@@ -1798,7 +1798,7 @@ SELECT 3 OPERATOR(pg_catalog.+) 4;
     <primary>privilege</primary>
     <secondary sortas="schemas">for schemas</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     By default, users cannot access any objects in schemas they do not
     own.  To allow that, the owner of the schema must grant the
@@ -1835,7 +1835,7 @@ REVOKE CREATE ON SCHEMA public FROM PUBLIC;
     <primary>system catalog</primary>
     <secondary>schema</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     In addition to <literal>public</> and user-created schemas, each
     database contains a <literal>pg_catalog</> schema, which contains
@@ -1867,7 +1867,7 @@ REVOKE CREATE ON SCHEMA public FROM PUBLIC;
 
   <sect2 id="ddl-schemas-patterns">
    <title>Usage Patterns</title>
-
+  &pgnotice;
    <para>
     Schemas can be used to organize your data in many ways.  There are
     a few usage patterns that are recommended and are easily supported by
@@ -1917,7 +1917,7 @@ REVOKE CREATE ON SCHEMA public FROM PUBLIC;
 
   <sect2 id="ddl-schemas-portability">
    <title>Portability</title>
-
+  &pgnotice;
    <para>
     In the SQL standard, the notion of objects in the same schema
     being owned by different users does not exist.  Moreover, some
@@ -1959,7 +1959,7 @@ REVOKE CREATE ON SCHEMA public FROM PUBLIC;
    <primary>table</primary>
    <secondary>inheritance</secondary>
   </indexterm>
-
+  &pgnotice;
   <para>
    <productname>PostgreSQL</productname> implements table inheritance,
    which can be a useful tool for database designers.  (SQL:1999 and
@@ -2190,7 +2190,7 @@ VALUES ('New York', NULL, NULL, 'NY');
 
  <sect2 id="ddl-inherit-caveats">
   <title>Caveats</title>
-
+  &pgnotice;
   <para>
    Note that not all SQL commands are able to work on
    inheritance hierarchies.  Commands that are used for data querying,
@@ -2281,7 +2281,7 @@ VALUES ('New York', NULL, NULL, 'NY');
     <primary>table</primary>
     <secondary>partitioning</secondary>
    </indexterm>
-
+  &pgnotice;
    <para>
     <productname>PostgreSQL</productname> supports basic table
     partitioning. This section describes why and how to implement
@@ -2290,7 +2290,7 @@ VALUES ('New York', NULL, NULL, 'NY');
 
    <sect2 id="ddl-partitioning-overview">
      <title>Overview</title>
-
+  &pgnotice;
    <para>
     Partitioning refers to splitting what is logically one large table
     into smaller physical pieces.
@@ -2384,7 +2384,7 @@ VALUES ('New York', NULL, NULL, 'NY');
 
    <sect2 id="ddl-partitioning-implementation">
      <title>Implementing Partitioning</title>
-
+  &pgnotice;
     <para>
      To set up a partitioned table, do the following:
      <orderedlist spacing="compact">
@@ -2679,7 +2679,7 @@ LANGUAGE plpgsql;
 
    <sect2 id="ddl-partitioning-managing-partitions">
    <title>Managing Partitions</title>
-
+  &pgnotice;
    <para>
      Normally the set of partitions established when initially
      defining the table are not intended to remain static. It is
@@ -2750,7 +2750,7 @@ ALTER TABLE measurement_y2008m02 INHERIT measurement;
    <indexterm>
     <primary>constraint exclusion</primary>
    </indexterm>
-
+  &pgnotice;
    <para>
     <firstterm>Constraint exclusion</> is a query optimization technique
     that improves performance for partitioned tables defined in the
@@ -2841,7 +2841,7 @@ EXPLAIN SELECT count(*) FROM measurement WHERE logdate &gt;= DATE '2008-01-01';
 
    <sect2 id="ddl-partitioning-alternatives">
    <title>Alternative Partitioning Methods</title>
-
+  &pgnotice;
     <para>
      A different approach to redirecting inserts into the appropriate
      partition table is to set up rules, instead of a trigger, on the
@@ -2903,7 +2903,7 @@ UNION ALL SELECT * FROM measurement_y2008m01;
 
    <sect2 id="ddl-partitioning-caveats">
    <title>Caveats</title>
-
+  &pgnotice;
    <para>
     The following caveats apply to partitioned tables:
    <itemizedlist>
@@ -2988,7 +2988,7 @@ ANALYZE measurement;
 
  <sect1 id="ddl-others">
   <title>Other Database Objects</title>
-
+  &pgnotice;
   <para>
    Tables are the central objects in a relational database structure,
    because they hold your data.  But they are not the only objects
@@ -3042,7 +3042,7 @@ ANALYZE measurement;
    <primary>RESTRICT</primary>
    <secondary sortas="DROP">with DROP</secondary>
   </indexterm>
-
+  &pgnotice;
   <para>
    When you create complex database structures involving many tables
    with foreign key constraints, views, triggers, functions, etc. you
diff --git a/doc/src/sgml/dfunc.sgmlin b/doc/src/sgml/dfunc.sgmlin
index 310787a..7f6fbac 100644
--- a/doc/src/sgml/dfunc.sgmlin
+++ b/doc/src/sgml/dfunc.sgmlin
@@ -2,7 +2,7 @@
 
 <sect2 id="dfunc">
  <title>Compiling and Linking Dynamically-Loaded Functions</title>
-
+  &pgnotice;
  <para>
   Before you are able to use your
   <productname>PostgreSQL</productname> extension functions written in
diff --git a/doc/src/sgml/dict-int.sgmlin b/doc/src/sgml/dict-int.sgmlin
index d19487f..23200cf 100644
--- a/doc/src/sgml/dict-int.sgmlin
+++ b/doc/src/sgml/dict-int.sgmlin
@@ -6,7 +6,7 @@
  <indexterm zone="dict-int">
   <primary>dict_int</primary>
  </indexterm>
-
+  &pgnotice;
  <para>
   <filename>dict_int</> is an example of an add-on dictionary template
   for full-text search.  The motivation for this example dictionary is to
@@ -17,7 +17,7 @@
 
  <sect2>
   <title>Configuration</title>
-
+  &pgnotice;
   <para>
    The dictionary accepts two options:
   </para>
@@ -45,7 +45,7 @@
 
  <sect2>
   <title>Usage</title>
-
+  &pgnotice;
   <para>
    Running the installation script creates a text search template
    <literal>intdict_template</> and a dictionary <literal>intdict</>
diff --git a/doc/src/sgml/dict-xsyn.sgmlin b/doc/src/sgml/dict-xsyn.sgmlin
index e1ec8e5..96a9f3d 100644
--- a/doc/src/sgml/dict-xsyn.sgmlin
+++ b/doc/src/sgml/dict-xsyn.sgmlin
@@ -6,7 +6,7 @@
  <indexterm zone="dict-xsyn">
   <primary>dict_xsyn</primary>
  </indexterm>
-
+  &pgnotice;
  <para>
   <filename>dict_xsyn</> (Extended Synonym Dictionary) is an example of an
   add-on dictionary template for full-text search.  This dictionary type
@@ -16,7 +16,7 @@
 
  <sect2>
   <title>Configuration</title>
-
+  &pgnotice;
   <para>
    A <literal>dict_xsyn</> dictionary accepts the following options:
   </para>
@@ -85,7 +85,7 @@ word syn1 syn2 syn3
 
  <sect2>
   <title>Usage</title>
-
+  &pgnotice;
   <para>
    Running the installation script creates a text search template
    <literal>xsyn_template</> and a dictionary <literal>xsyn</>
diff --git a/doc/src/sgml/diskusage.sgmlin b/doc/src/sgml/diskusage.sgmlin
index 0c7f544..fdf89db 100644
--- a/doc/src/sgml/diskusage.sgmlin
+++ b/doc/src/sgml/diskusage.sgmlin
@@ -2,7 +2,7 @@
 
 <chapter id="diskusage">
  <title>Monitoring Disk Usage</title>
-
+  &pgnotice;
  <para>
   This chapter discusses how to monitor the disk usage of a
   <productname>PostgreSQL</> database system.
@@ -14,7 +14,7 @@
   <indexterm zone="disk-usage">
    <primary>disk usage</primary>
   </indexterm>
-
+  &pgnotice;
   <para>
    Each table has a primary heap disk file where most of the data is
    stored. If the table has any columns with potentially-wide values,
@@ -112,7 +112,7 @@ ORDER BY relpages DESC;
 
  <sect1 id="disk-full">
   <title>Disk Full Failure</title>
-
+  &pgnotice;
   <para>
    The most important disk monitoring task of a database administrat...
 
[truncated message content]

2010	Jan	Feb	Mar	Apr (4)	May (28)	Jun (12)	Jul (11)	Aug (12)	Sep (5)	Oct (19)	Nov (14)	Dec (12)
2011	Jan (18)	Feb (30)	Mar (115)	Apr (89)	May (50)	Jun (44)	Jul (22)	Aug (13)	Sep (11)	Oct (30)	Nov (28)	Dec (39)
2012	Jan (38)	Feb (18)	Mar (43)	Apr (91)	May (108)	Jun (46)	Jul (37)	Aug (44)	Sep (33)	Oct (29)	Nov (36)	Dec (15)
2013	Jan (35)	Feb (611)	Mar (5)	Apr (55)	May (30)	Jun (28)	Jul (458)	Aug (34)	Sep (9)	Oct (39)	Nov (22)	Dec (32)
2014	Jan (16)	Feb (16)	Mar (42)	Apr (179)	May (7)	Jun (6)	Jul (9)	Aug	Sep (4)	Oct	Nov (3)	Dec
2015	Jan	Feb	Mar	Apr (2)	May (4)	Jun	Jul	Aug	Sep	Oct	Nov	Dec

S	M	T	W	T	F	S
1	2 (1)	3 (3)	4 (3)	5	6	7
8	9 (1)	10 (1)	11 (3)	12 (4)	13	14
15	16 (1)	17	18	19 (1)	20	21
22	23	24 (7)	25 (16)	26 (2)	27	28
29	30 (4)	31 (3)

postgres-xc-committers Mailing List for Postgres-XC

postgres-xc-committers — Announces PG-XC repository commits