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 1iSjJp-0003gf-Rq for pgsql-docs@arkaria.postgresql.org; Thu, 07 Nov 2019 15:03:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iSjJo-0007AF-K8 for pgsql-docs@arkaria.postgresql.org; Thu, 07 Nov 2019 15:03:28 +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 1iSjJn-00079o-UJ for pgsql-docs@lists.postgresql.org; Thu, 07 Nov 2019 15:03:28 +0000 Received: from mail-qv1-xf41.google.com ([2607:f8b0:4864:20::f41]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1iSjJl-0004Fb-32 for pgsql-docs@lists.postgresql.org; Thu, 07 Nov 2019 15:03:26 +0000 Received: by mail-qv1-xf41.google.com with SMTP id y18so910416qve.2 for ; Thu, 07 Nov 2019 07:03:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=lNovrAEtM353g+r15yyfoRHgaMHjpGTOIguGfUGU810=; b=HPYIIuctParhslyAorN2fV7NmlH5RUYtheEJ6bK9O9+LDfe8s0PHqxBojElG33LnGd 10yw1aArCJhuUyslbFYPP3oIxDIfhtmeIZEgy9522zutXuhYpXH2a8AlBbcqhx646r3w ERJqw3Z74F3ny4ydgew6+WHyUwZJZsJDUjBCyavAcLsNHhcSERqasTUdGmT6bQv9Zfgz x2ndxchuRgAAM3maBeLdBlQP0tTVIslc+w/W/2U4oTIxfwYyBBmg1LVYsQ7bT3ahvOhw Nl1mSguUrowB8N2nVmOCJm6b2BGc3KLv1uqD6I4uFb3d+EP8OjoYFnypi6gXfEQXI6RS WCWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=lNovrAEtM353g+r15yyfoRHgaMHjpGTOIguGfUGU810=; b=t6KyiDmzJV6AIUHAducvm12YKdhDV6px0iVK/NRjdp8Gdr1H+rpck3pMuBORDI3Cfo 7zv3pQblOvmbmJi6FOEcTmfyr/9vDlXe7tbFtO4DV1l9OE0ynOcwSPr3opaUe5Y2/pgA qphyZdgDsF0rPohSo1vP8hz85BmWYuIXvYSpNK+mTfwUZ2DXQ3+D7nJkxYFCVkluxKi/ XJ0uRTQDi/OlRBrJBcEDpgeriLRTVgnTLXvghwlGpspye4z9YwamVSBmQBgRY+2LIfLJ 1kGvJUH3l6WL+fwps21RZ1CdKVuDutqfqV8r4XJW9oG90Si7ozkmACMLYs7uIodOqrd3 PVGw== X-Gm-Message-State: APjAAAV6CaHcqIu0GNnL5PGpljiIHl2+990n2iBMss/GuYEjXVNFpH47 xnXveIH9MHmLnOe9s5kfB35hoClNDVmLfihBBYtGg3Ssedcocxn1uCj+88Oq86jvDBm/SCIEKEJ GHBB2eVCH/BpuFi5gy8BRpOyiU+HVMYE5UlEbysOJMCk7Fl3WbnLN5ta2FuvTMtVciULROSh8QC 3fGwWX8a+YHQ== X-Google-Smtp-Source: APXvYqx1p499KePv8vtOyUKHSEhxAVvcJAuQer63bvePfYzHxIFTHseszlRgwBLV/X9VcKSTYpo6jA== X-Received: by 2002:ad4:43e5:: with SMTP id f5mr3771039qvu.37.1573139003805; Thu, 07 Nov 2019 07:03:23 -0800 (PST) Received: from nimloth.alvh.no-ip.org (ip-104-2-52-196.nyc.us.northamericancoax.com. [196.52.2.104]) by smtp.gmail.com with ESMTPSA id x25sm1019539qki.63.2019.11.07.07.03.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 07 Nov 2019 07:03:23 -0800 (PST) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 4C9523015CB; Thu, 7 Nov 2019 12:03:20 -0300 (-03) Date: Thu, 7 Nov 2019 12:03:20 -0300 From: Alvaro Herrera To: brian.williams@mayalane.com, pgsql-docs@lists.postgresql.org Subject: Re: The word "virgin" used incorrectly and probably better off replaced Message-ID: <20191107150320.GA8132@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <157313712259.14261.16141263269989647311@wrigleys.postgresql.org> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-Nov-07, PG Doc comments form wrote: > Page: https://www.postgresql.org/docs/12/manage-ag-templatedbs.html > Description: > > The use of the word virgin as an adjective is incorrect here and also an > anachronism. It is better off replaced with the word pristine - quotes > unnecessary. Note the word virgin appears in another page of the > documentation (a search will find it). Just because a word has sexual connotations does not imply that it doesn't have non-sexual meanings. Merriam-Webster lists https://www.merriam-webster.com/dictionary/virgin 2: FRESH, UNSPOILED specifically : not altered by human activity 6: free of impurity or stain : UNSULLIED which seems to apply well to all cases at hand. Also: First Known Use of virgin Noun: 13th century, in the meaning defined at sense 2a Adjective: 14th century, in the meaning defined at sense 6 History and Etymology for virgin Noun: Middle English, from Anglo-French virgine, from Latin virgin-, virgo young woman, virgin That said, in two of the three phrases where the word appears, the quoted adjective adds no value. We could remove the quoted word entirely in all three places and nothing would be lost. But if we do that, then the third occurrence of the word would become inintelligible: "This is particularly handy when restoring a pg_dump dump: the dump script should be restored in a virgin database to ensure that one recreates the correct contents of the dumped database, without conflicting with objects that might have been added to template1 later on." because we have not explained what a "virgin database" is. We could say "empty", which seems better suited than both "virgin" and "pristine" anyway. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services