Re: fix typos
John Naylor <john.naylor@enterprisedb.com>
From: John Naylor <john.naylor@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Justin Pryzby <pryzby@telsasoft.com>, Erik Rijkers <er@xs4all.nl>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-08-16T01:48:27Z
Lists: pgsql-hackers
Attachments
- v1-consistently-refer-to-roident-as-ID-in-messages-and-docs.patch (text/x-patch) patch v1
On Fri, Aug 12, 2022 at 8:55 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > 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". The documentation has both, so it makes sense to standardize on "ID". The messages all had oid/OID, which I changed in the attached. I think I got all the places. I'm thinking it's not wrong enough to confuse people, but consistency is good, so backpatch to v15 and no further. Does anyone want to make a case otherwise? -- John Naylor EDB: http://www.enterprisedb.com
Commits
-
Fix formatting and comment typos
- bcabbfc6a94b 16.0 landed
-
Fix assorted doc typos
- 120e159b7d93 14.5 landed
- b25566ab3c65 15.0 landed
- 9f08803828d7 16.0 landed
-
Clarify DROP EXTENSION docs regarding explicitly dependent routines
- d107e73fa8b5 14.5 landed
- 0436f34d406a 15.0 landed
- f217d093fd61 16.0 landed
-
doc: clarify how dropping of extensions affects dependent objs.
- 5fe2d4c56edd 16.0 cited
-
Move remaining code from tqual.[ch] to heapam.h / heapam_visibility.c.
- c91560defc57 12.0 cited