From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
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 23:05:16 |
Message-ID: | 20191107230516.GF487@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Thu, Nov 7, 2019 at 06:50:10PM -0300, Alvaro Herrera wrote:
> 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."
True.
--
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 +
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-11-08 00:05:19 | Re: wal_sender_timeout / wal_receiver_timeout - seconds or milliseconds? |
Previous Message | Bruce Momjian | 2019-11-07 22:36:17 | Re: wal_sender_timeout / wal_receiver_timeout - seconds or milliseconds? |