diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2019-11-14 17:33:26 -0300 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2019-11-14 17:33:26 -0300 |
| commit | 6ae4d271879b62c4325df3ddf75bff3f2b911086 (patch) | |
| tree | 6ecfc6fa0afa92b25294ded6e9a84f4c261f01c9 /doc/src | |
| parent | 50d22de9325f41a32faeb0d1055f50b43d0507b3 (diff) | |
| download | postgresql-6ae4d271879b62c4325df3ddf75bff3f2b911086.tar.gz postgresql-6ae4d271879b62c4325df3ddf75bff3f2b911086.zip | |
Remove the word "virgins" for documentation
Apparently, it's no longer welcome. Therefore replace it with "pristine",
and add some explanatory text while at it.
Reported by Brian Williams
Discussion: https://postgr.es/m/157313712259.14261.16141263269989647311@wrigleys.postgresql.org
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/manage-ag.sgml | 7 | ||||
| -rw-r--r-- | doc/src/sgml/ref/create_database.sgml | 6 |
2 files changed, 8 insertions, 5 deletions
diff --git a/doc/src/sgml/manage-ag.sgml b/doc/src/sgml/manage-ag.sgml index 0154064e506..b1b8539fb3a 100644 --- a/doc/src/sgml/manage-ag.sgml +++ b/doc/src/sgml/manage-ag.sgml @@ -199,11 +199,12 @@ createdb -O <replaceable>rolename</replaceable> <replaceable>dbname</replaceable should never be changed after the database cluster has been initialized. By instructing <command>CREATE DATABASE</command> to copy <literal>template0</literal> instead - of <literal>template1</literal>, you can create a <quote>virgin</quote> user - database that contains none of the site-local additions in + of <literal>template1</literal>, you can create a <quote>pristine</quote> user + database (one where no user-defined objects exist and where the system + objects have not been altered) that contains none of the site-local additions in <literal>template1</literal>. This is particularly handy when restoring a <literal>pg_dump</literal> dump: the dump script should be restored in a - virgin database to ensure that one recreates the correct contents + pristine database to ensure that one recreates the correct contents of the dumped database, without conflicting with objects that might have been added to <literal>template1</literal> later on. </para> diff --git a/doc/src/sgml/ref/create_database.sgml b/doc/src/sgml/ref/create_database.sgml index 4014f6703bb..504c1b02246 100644 --- a/doc/src/sgml/ref/create_database.sgml +++ b/doc/src/sgml/ref/create_database.sgml @@ -54,8 +54,10 @@ CREATE DATABASE <replaceable class="parameter">name</replaceable> system database <literal>template1</literal>. A different template can be specified by writing <literal>TEMPLATE <replaceable class="parameter">name</replaceable></literal>. In particular, - by writing <literal>TEMPLATE template0</literal>, you can create a virgin - database containing only the standard objects predefined by your + by writing <literal>TEMPLATE template0</literal>, you can create a pristine + database (one where no user-defined objects exist and where the system + objects have not been altered) + containing only the standard objects predefined by your version of <productname>PostgreSQL</productname>. This is useful if you wish to avoid copying any installation-local objects that might have been added to |