Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iT00r-0007Dr-KZ for pgsql-docs@arkaria.postgresql.org; Fri, 08 Nov 2019 08:53:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iT00q-0006jl-Ey for pgsql-docs@arkaria.postgresql.org; Fri, 08 Nov 2019 08:53:00 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iT00q-0006jW-3b for pgsql-docs@lists.postgresql.org; Fri, 08 Nov 2019 08:53:00 +0000 Received: from smtp2.outgoing.loopia.se ([93.188.3.37]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iT00m-0004rL-OK for pgsql-docs@lists.postgresql.org; Fri, 08 Nov 2019 08:52:58 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id E2CA42E4F0A6 for ; Fri, 8 Nov 2019 09:52:49 +0100 (CET) Received: from s645.loopia.se (unknown [172.22.191.5]) by s807.loopia.se (Postfix) with ESMTP id C2EB32E27620; Fri, 8 Nov 2019 09:52:49 +0100 (CET) Received: from s476.loopia.se (unknown [172.22.191.6]) by s645.loopia.se (Postfix) with ESMTP id ACB9A156E4EE; Fri, 8 Nov 2019 09:52:49 +0100 (CET) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1 X-Spam-Level: X-Spam-Status: No, score=-1 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1] autolearn=disabled Received: from s630.loopia.se ([172.22.191.6]) by s476.loopia.se (s476.loopia.se [172.22.190.16]) (amavisd-new, port 10024) with LMTP id sPM3EXbIzF09; Fri, 8 Nov 2019 09:52:49 +0100 (CET) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.199 Received: from [192.168.72.43] (customer-89-255-232-199.stosn.net [89.255.232.199]) (Authenticated sender: daniel@yesql.se) by s630.loopia.se (Postfix) with ESMTPSA id 2E00913ABDB3; Fri, 8 Nov 2019 09:52:49 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: The word "virgin" used incorrectly and probably better off replaced From: Daniel Gustafsson In-Reply-To: <20191107215010.GA8541@alvherre.pgsql> Date: Fri, 8 Nov 2019 09:52:48 +0100 Cc: Bruce Momjian , brian.williams@mayalane.com, pgsql-docs@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20191107215010.GA8541@alvherre.pgsql> To: Alvaro Herrera X-Mailer: Apple Mail (2.3445.104.11) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk > On 7 Nov 2019, at 22:50, Alvaro Herrera = wrote: >=20 > On 2019-Nov-07, Bruce Momjian wrote: >=20 >> On Thu, Nov 7, 2019 at 07:55:22PM +0100, Daniel Gustafsson wrote: >>>> On 7 Nov 2019, at 16:03, Alvaro Herrera = wrote: >=20 >>>> We could say "empty", which seems better suited than both "virgin" = and >>>> "pristine" anyway. >>>=20 >>> empty is a lot better, but still isn't conveying the state of the = database >>> without there being room for interpretation. (My grasp of the = english language >>> isn't enough to suggest a better alternative however). >>=20 >> I am thinking "pristine" would be a good word here. >=20 > But you would have to explain that a database created as a copy of > template1 may somehow not be pristine. Maybe we should just use a > phrase that describes what we mean, something like "a database that > doesn't contain objects other than default system ones." Agreed. I like your suggestion, or the inverse of it: "a database = without any user defined objects". cheers ./daniel=