Re: Row pattern recognition

Tatsuo Ishii <ishii@postgresql.org>

From: Tatsuo Ishii <ishii@postgresql.org>
To: assam258@gmail.com
Cc: michael@paquier.xyz, ishii@postgresql.org, jacob.champion@enterprisedb.com, david.g.johnston@gmail.com, vik@postgresfriends.org, er@xs4all.nl, peter@eisentraut.org, pgsql-hackers@postgresql.org
Date: 2026-01-20T00:37:04Z
Lists: pgsql-hackers
>> Note: this message is clearly AI-generated to me, and these are
>> usually super sloppy.  (I'd suggest to stop posting semi-generated
>> messages as they tend to be made of mostly unhelpful contents as they
>> lack judgement and context, but there's no rule against that AFAIK
>> around here, as well.)
>>
> 
> Fair point. I can read technical documentation but lack
> English communication skills, so I rely on AI for
> translation. Actually, AI is what enabled me to start
> contributing to PostgreSQL in the first place. I'll try
> to make future posts more readable.

Using AI for translation is no problem for me. In fact, since I am not
good at English, sometimes I am googling to look for good translation
of a sentence in my message.

Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Adjust cross-version upgrade tests for seg_out() fix

  2. Rationalize error comments in partition split/merge tests

  3. Add fast path for foreign key constraint checks

  4. Fix assorted pretty-trivial memory leaks in the backend.

  5. Add temporal FOREIGN KEY contraints

  6. Add trailing commas to enum definitions

  7. Remove obsolete executor cleanup code