Re: The word "virgin" used incorrectly and probably better off replaced
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Daniel Gustafsson <daniel@yesql.se>, Bruce Momjian <bruce@momjian.us>, brian.williams@mayalane.com, pgsql-docs@lists.postgresql.org
Date: 2019-11-08T16:30:07Z
Lists: pgsql-docs
Attachments
- v2-0001-No-more-virgins.patch (text/x-diff) patch v2-0001
On 2019-Nov-08, Tom Lane wrote: > Alvaro Herrera <alvherre@2ndquadrant.com> writes: > > Hmm. Maybe we can say "pristine database" and then add this explanation > > in a parenthical comment: > > > This is particularly handy when restoring a > > <literal>pg_dump</literal> dump: the dump script should be restored in a > > pristine database (one where no user-defined objects exist and where > > system objects have not been altered), 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. > > So the patch becomes s/virgin/pristine/g plus add a parenthetical > definition for the first use? Works for me. Well, there are three uses of the word "virgin". The first is for "virgin user", and the patch turns that into just "user". The second one is for "virgin database" and the patch has the effect you describe. The third one is also s/virgin//. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Remove the word "virgins" for documentation
- 6ae4d271879b 13.0 landed