Date: Thu, 19 Mar 2020 12:37:22 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: Re: "Cannot" vs "could not"
Message-ID: <20200319163722.GD2571@momjian.us>
References: <20200319155704.GC2571@momjian.us>
 <25965.1584634055@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <25965.1584634055@sss.pgh.pa.us>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On Thu, Mar 19, 2020 at 12:07:35PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > We use "cannot" and "could not" quite often in source code and error
> > messages:
> 
> Yup.
> 
> > Is there any sense that we should have more consistency in our message
> > wording?
> 
> There is specific guidance about it in our error message style guide:
> 
> https://www.postgresql.org/docs/devel/error-style-guide.html
> 
> (see under "Present vs. Past Tense").  I believe we largely conform
> to that guideline, though of course exceptions sneak in from time
> to time.

Oh, good. I remember we discussed this in the past, but didn't realize
we had written it down.  Thanks.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

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