Re: Row pattern recognition

Tatsuo Ishii <ishii@postgresql.org>

From: Tatsuo Ishii <ishii@postgresql.org>

To: assam258@gmail.com

Cc: vik@postgresfriends.org, er@xs4all.nl, jacob.champion@enterprisedb.com, david.g.johnston@gmail.com, peter@eisentraut.org, pgsql-hackers@postgresql.org

Date: 2026-02-24T11:44:17Z

Lists: pgsql-hackers

Attachments

(unnamed) (text/plain)

Hi Henson,

Currently we do not account the cost of RPR while planning.  Attached
is the first attempt to try to estimate the RPR costs. The cost model
is very simple:

expression cost per PATTERN variable * number of input tuples

Any idea to make this estimation better?

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 →

Adjust cross-version upgrade tests for seg_out() fix
- 3e3d7875e956 19 (unreleased) cited
Rationalize error comments in partition split/merge tests
- ecb2508aaf9b 19 (unreleased) cited
Add fast path for foreign key constraint checks
- 2da86c1ef9b5 19 (unreleased) cited
Fix assorted pretty-trivial memory leaks in the backend.
- e78d1d6d47dc 19 (unreleased) cited
Add temporal FOREIGN KEY contraints
- 89f908a6d0ac 18.0 cited
Add trailing commas to enum definitions
- 611806cd726f 17.0 cited
Remove obsolete executor cleanup code
- d060e921ea5a 17.0 cited