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 1iSmwP-0003ck-0b for pgsql-docs@arkaria.postgresql.org; Thu, 07 Nov 2019 18:55:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iSmwN-0007uR-Pq for pgsql-docs@arkaria.postgresql.org; Thu, 07 Nov 2019 18:55:31 +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 1iSmwN-0007uK-FJ for pgsql-docs@lists.postgresql.org; Thu, 07 Nov 2019 18:55:31 +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 1iSmwJ-0006X6-VF for pgsql-docs@lists.postgresql.org; Thu, 07 Nov 2019 18:55:30 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id E3A352E4B7C1 for ; Thu, 7 Nov 2019 19:55:23 +0100 (CET) Received: from s630.loopia.se (unknown [172.22.191.5]) by s807.loopia.se (Postfix) with ESMTP id C522F2E2874D; Thu, 7 Nov 2019 19:55:23 +0100 (CET) Received: from s473.loopia.se (unknown [172.22.191.5]) by s630.loopia.se (Postfix) with ESMTP id B1F9913ABD83; Thu, 7 Nov 2019 19:55:23 +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 s498.loopia.se ([172.22.191.6]) by s473.loopia.se (s473.loopia.se [172.22.190.13]) (amavisd-new, port 10024) with LMTP id ppFFMikABAXE; Thu, 7 Nov 2019 19:55:23 +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 s498.loopia.se (Postfix) with ESMTPSA id 54DEE470747; Thu, 7 Nov 2019 19:55:23 +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: <20191107150320.GA8132@alvherre.pgsql> Date: Thu, 7 Nov 2019 19:55:22 +0100 Cc: brian.williams@mayalane.com, pgsql-docs@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <3F23BAF9-F616-4B7A-9072-C59349F517E7@yesql.se> References: <20191107150320.GA8132@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 16:03, Alvaro Herrera = wrote: > because we have not explained what a "virgin database" is. =20 I think this is the key observation. > We could say "empty", which seems better suited than both "virgin" and > "pristine" anyway. 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). cheers ./daniel=