Re: Row pattern recognition
Henson Choi <assam258@gmail.com>
From: Henson Choi <assam258@gmail.com>
To: Tatsuo Ishii <ishii@postgresql.org>
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-27T05:44:01Z
Lists: pgsql-hackers
Hi Tatsuo, The standard does not allow to use range variables, declared in the > FROM clause, in the DEFINE clause (19075-5 6.5). Attached patch raises > an error in this case. > Agreed. §6.5 is explicit about mutual exclusivity of the two sets of range variables. Your patch is correct for this case. Also, currently we do not support pattern variable range vars in the > DEFINE caluse (e.g. UP.price). If used, we see a confusing error > message: > > ERROR: missing FROM-clause entry for table "UP" > LINE 13: UP AS UP.price > PREV(price), > ^ > Pattern variable qualified names like `UP.price` are actually valid standard syntax (§4.16 uses them in examples), so "is not allowed" is misleading — "is not supported" would be more accurate. To distinguish the two cases, we could expose `patternVarNames` via ParseState (it is already collected by `validateRPRPatternVarCount` before DEFINE expressions are transformed) and check in `transformColumnRef` whether the qualifier is a pattern variable: - pattern variable qualifier → "not supported" - anything else → "not allowed" Would it be okay if I revise the patch along those lines? Best regards, Henson
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