Re: The word "virgin" used incorrectly and probably better off replaced

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, brian(dot)williams(at)mayalane(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: The word "virgin" used incorrectly and probably better off replaced
Date: 2019-11-07 21:27:50
Message-ID: 20191107212750.GB487@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Thu, Nov 7, 2019 at 07:55:22PM +0100, Daniel Gustafsson wrote:
> > On 7 Nov 2019, at 16:03, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
>
> > because we have not explained what a "virgin database" is.
>
> 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).

I am thinking "pristine" would be a good word here.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Alvaro Herrera 2019-11-07 21:50:10 Re: The word "virgin" used incorrectly and probably better off replaced
Previous Message Bruce Momjian 2019-11-07 21:26:55 Re: Does 'instead of delete' trigger support modification of OLD