From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, 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:50:10 |
Message-ID: | 20191107215010.GA8541@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 2019-Nov-07, Bruce Momjian wrote:
> 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:
> > > 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.
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."
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2019-11-07 22:28:18 | Re: Does 'instead of delete' trigger support modification of OLD |
Previous Message | Bruce Momjian | 2019-11-07 21:27:50 | Re: The word "virgin" used incorrectly and probably better off replaced |