Date: Thu, 19 Mar 2020 11:57:04 -0400
From: Bruce Momjian <bruce@momjian.us>
To: PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: "Cannot" vs "could not"
Message-ID: <20200319155704.GC2571@momjian.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

We use "cannot" and "could not" quite often in source code and error
messages:

	$ grep .. 'cannot' | wc -l
	13180

	$ grep ... 'could not' | wc -l
	12149

I noticed it by looking for errors about parsing in our /bin tools:

	src/pl/plperl/ppport.h:      die "cannot parse version '$ver'\n";
	src/pl/plperl/ppport.h:      die "cannot parse version '$ver'\n";
	src/bin/pg_upgrade/server.c: pg_fatal("could not parse version file \"%s\"\n", cluster->pgdata);

This web page explains the difference well, i.e., "cannot" is present
tens, "could not" is past tense:

	https://www.englishforums.com/English/CannotVsCouldNot/bhprvk/post.htm

Is there any sense that we should have more consistency in our message
wording?

-- 
  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 +