Re: [PATCH v1] Fixed a spelling error in the comments in gininsert.c

Chao Li <li.evan.chao@gmail.com>

From: Chao Li <li.evan.chao@gmail.com>

To: Michael Paquier <michael@paquier.xyz>

Cc: Tender Wang <tndrwang@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-12-20T00:31:28Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix another typo in gininsert.c
- d31276f0e290 19 (unreleased) landed
Fix typos in gininsert.c
- 5cdbec5aa9dc 19 (unreleased) landed


> On Dec 20, 2025, at 08:24, Michael Paquier <michael@paquier.xyz> wrote:
> 
> On Fri, Dec 19, 2025 at 01:55:14PM +0800, Tender Wang wrote:
>> I just found another typo in gininsert.c(maybe on a new thread)
>> Comments for _gin_build_tuple():
>> 
>> "
>> * For by-reference data types, we store the actual data. For by-val types
>> * we simply copy the whole Datum, so that we don't have to care about stuff
>> * like endianess etc.
>> "
>> 
>> "endianess" should be "endianness".
> 
> Indeed.  Thanks.
> --
> Michael

I found that earlier, but when I checked with https://www.onelook.com/?w=endianess, it has two matches, so I guessed that spelling is acceptable.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/