Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1jExht-0008Nr-Q3 for pgsql-docs@arkaria.postgresql.org; Thu, 19 Mar 2020 16:07:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jExhs-0000ee-Kt for pgsql-docs@arkaria.postgresql.org; Thu, 19 Mar 2020 16:07:40 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1jExhs-0000eX-Dj for pgsql-docs@lists.postgresql.org; Thu, 19 Mar 2020 16:07:40 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jExhp-0000de-IL for pgsql-docs@postgresql.org; Thu, 19 Mar 2020 16:07:40 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 02JG7ZOQ025966; Thu, 19 Mar 2020 12:07:35 -0400 From: Tom Lane To: Bruce Momjian cc: PostgreSQL-documentation Subject: Re: "Cannot" vs "could not" In-reply-to: <20200319155704.GC2571@momjian.us> References: <20200319155704.GC2571@momjian.us> Comments: In-reply-to Bruce Momjian message dated "Thu, 19 Mar 2020 11:57:04 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <25964.1584634055.1@sss.pgh.pa.us> Date: Thu, 19 Mar 2020 12:07:35 -0400 Message-ID: <25965.1584634055@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Bruce Momjian 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. regards, tom lane