Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1oMV8N-0005Xj-Ml
	for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Aug 2022 13:55:31 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1oMV8M-0005JN-J5
	for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Aug 2022 13:55:30 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1oMV8M-0005JE-9o
	for pgsql-hackers@lists.postgresql.org; Fri, 12 Aug 2022 13:55:30 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1oMV8E-0007dr-ND
	for pgsql-hackers@lists.postgresql.org; Fri, 12 Aug 2022 13:55:28 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 27CDtJki133550;
	Fri, 12 Aug 2022 09:55:19 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: John Naylor <john.naylor@enterprisedb.com>
cc: Justin Pryzby <pryzby@telsasoft.com>, Erik Rijkers <er@xs4all.nl>,
        PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: fix typos
In-reply-to: 
 <CAFBsxsHw8662UQSj_gf6Z+_6s1xnopS2uJxZ78b4YSMw3PdVSQ@mail.gmail.com>
References: <b79bfeff-d0e3-29a3-2576-0e325848dede@xs4all.nl>
 <20220801181136.GJ15006@telsasoft.com>
 <CAFBsxsGeWFdz0kTWDN5HU4qhBJdJjU+aDookfofha80rqvieMA@mail.gmail.com>
 <3437166.1659620465@sss.pgh.pa.us>
 <CAFBsxsHvUEtG1QAfy0Vs-gvitnOJUuTzNSdzcyOHija5QGW-7g@mail.gmail.com>
 <CAFBsxsHw8662UQSj_gf6Z+_6s1xnopS2uJxZ78b4YSMw3PdVSQ@mail.gmail.com>
Comments: In-reply-to John Naylor <john.naylor@enterprisedb.com>
	message dated "Fri, 12 Aug 2022 13:59:30 +0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <133548.1660312519.1@sss.pgh.pa.us>
Date: Fri, 12 Aug 2022 09:55:19 -0400
Message-ID: <133549.1660312519@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: 
 <https://www.postgresql.org/message-id/133549.1660312519%40sss.pgh.pa.us>
Precedence: bulk

John Naylor <john.naylor@enterprisedb.com> writes:
> This is really a straw-man proposal, since I'm not volunteering to do
> the work, or suggest anybody else should do the same. That being the
> case, it seems we should just go ahead with Justin's patch for
> consistency. Possibly we could also change the messages to say "ID"?

I'd be content if we change the user-facing messages (and documentation
if any) to say "ID" not "OID".

			regards, tom lane