Re: Row pattern recognition

From: Henson Choi <assam258(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tatsuo Ishii <ishii(at)postgresql(dot)org>, jacob(dot)champion(at)enterprisedb(dot)com, david(dot)g(dot)johnston(at)gmail(dot)com, vik(at)postgresfriends(dot)org, er(at)xs4all(dot)nl, peter(at)eisentraut(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Row pattern recognition
Date: 2026-01-19 23:51:30
Message-ID: CAAAe_zD0Kxf1wjgad1tRdR6dyR6UEg1puNGQqnx_HCqLVX1K3w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Michael,

2026년 1월 20일 (화) AM 8:40, Michael Paquier <michael(at)paquier(dot)xyz>님이 작성:

> On Mon, Jan 19, 2026 at 12:32:40AM +0900, Henson Choi wrote:
> > I'm writing to document the detailed design of context absorption
> > optimization in Row Pattern Recognition (RPR). This is mainly for
> > future reference - honestly, I'm afraid I'll forget these details
> > myself in a few months, and I'd rather have them written down
> > somewhere public than buried in my notes. I don't want to repeat the
> > mistake of famous mathematical theorems
> > where brilliant ideas were lost because "the margin was too narrow
> > to contain the proof" (yes, I'm looking at you, Fermat!). I certainly
> > don't want future PostgreSQL hackers to spend the next 358 years
> > trying to re-implement context absorption because the design rationale
> > was lost. Fortunately, the PostgreSQL community has provided us with
> > sufficient digital margins. :)
>
> 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.

> --
> Michael
>

Thanks for the feedback.

Best regards,
Henson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2026-01-20 00:11:55 Re: More speedups for tuple deformation
Previous Message Michael Paquier 2026-01-19 23:40:43 Re: Row pattern recognition