Doc: clean up some places that mentioned template1 but not template0.

Improve old text that wasn't updated when we added template0 to
the standard database set.

Per suggestion from P. Luzanov.

Discussion: https://postgr.es/m/163583775122.675.3700595100340939507@wrigleys.postgresql.org

diff --git a/doc/src/sgml/manage-ag.sgml b/doc/src/sgml/manage-ag.sgml
index 74055a4706557ff3c6f33b7b116d5a28b58371b4..23f116befeb5249b27ee3a0ce43ac07d410d9b7c 100644 (file)
--- a/doc/src/sgml/manage-ag.sgml
+++ b/doc/src/sgml/manage-ag.sgml
@@ -136,15 +136,21 @@ CREATE DATABASE name;
   
 
   
-   A second database,
-   template1,template1
-   is also created during database cluster initialization.  Whenever a
+   Two additional databases,
+   template1template1
+   and
+   template0,template0
+   are also created during database cluster initialization.  Whenever a
    new database is created within the
    cluster, template1 is essentially cloned.
    This means that any changes you make in template1 are
    propagated to all subsequently created databases. Because of this,
    avoid creating objects in template1 unless you want them
-   propagated to every newly created database.  More details
+   propagated to every newly created database.
+   template0 is meant as a pristine copy of the original
+   contents of template1.  It can be cloned instead
+   of template1 when it is important to make a database
+   without any such site-local additions.  More details
    appear in .
   
 

diff --git a/doc/src/sgml/ref/initdb.sgml b/doc/src/sgml/ref/initdb.sgml
index 9d47cacbe0b70ed54d50cb4d022ef6aba1a81817..8f71c7c962dd7be92019b7cc59071d2e4845a241 100644 (file)
--- a/doc/src/sgml/ref/initdb.sgml
+++ b/doc/src/sgml/ref/initdb.sgml
@@ -46,13 +46,16 @@ PostgreSQL documentation
    Creating a database cluster consists of creating the directories in
    which the database data will live, generating the shared catalog
    tables (tables that belong to the whole cluster rather than to any
-   particular database), and creating the template1
-   and postgres databases. When you later create a
-   new database, everything in the template1 database is
-   copied.  (Therefore, anything installed in template1
-   is automatically copied into each database created later.)
+   particular database), and creating the postgres,
+   template1, and template0 databases.
    The postgres database is a default database meant
    for use by users, utilities and third party applications.
+   template1 and template0 are
+   meant as source databases to be copied by later CREATE
+   DATABASE commands.  template0 should never
+   be modified, but you can add objects to template1,
+   which by default will be copied into databases created later.  See
+    for more details.
   
 
   
@@ -88,7 +91,7 @@ PostgreSQL documentation
    collation order (LC_COLLATE) and character set classes
    (LC_CTYPE, e.g., upper, lower, digit) can be set separately
    for a database when it is created. initdb determines
-   those settings for the template1 database, which will
+   those settings for the template databases, which will
    serve as the default for all other databases.
   
 
@@ -184,9 +187,9 @@ PostgreSQL documentation
       --encoding=encoding
       
        
-        Selects the encoding of the template database. This will also
+        Selects the encoding of the template databases. This will also
         be the default encoding of any database you create later,
-        unless you override it there.  The default is derived from the locale, or
+        unless you override it then.  The default is derived from the locale, or
         SQL_ASCII if that does not work. The character sets supported by
         the PostgreSQL server are described
         in .

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index d74d1ed7afadfc06e64c71288824aaebf38dc7ed..58150996b802814dae489b923759a6aa256f31c3 100644 (file)
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -74,10 +74,10 @@
    which is meant as a default database for use by utilities, users and third
    party applications.  The database server itself does not require the
    postgres database to exist, but many external utility
-   programs assume it exists.  Another database created within each cluster
-   during initialization is called
-   template1.  As the name suggests, this will be used
-   as a template for subsequently created databases; it should not be
+   programs assume it exists.  There are two more databases created within
+   each cluster during initialization, named template1
+   and template0.  As the names suggest, these will be
+   used as templates for subsequently-created databases; they should not be
    used for actual work.  (See  for
    information about creating new databases within a cluster.)