| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | assam258(at)gmail(dot)com, jian(dot)universality(at)gmail(dot)com |
| Cc: | zsolt(dot)parragi(at)percona(dot)com, sjjang112233(at)gmail(dot)com, vik(at)postgresfriends(dot)org, er(at)xs4all(dot)nl, jacob(dot)champion(at)enterprisedb(dot)com, david(dot)g(dot)johnston(at)gmail(dot)com, peter(at)eisentraut(dot)org, li(dot)evan(dot)chao(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Row pattern recognition |
| Date: | 2026-09-26 11:53:23 |
| Message-ID: | 20260926.205323.567735777208602850.ishii@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Currently the keyword RUNNING with row pattern navigation in the
DEFINE clause is not supported. (As FINAL can only be used in
MEASURES clause and we do not support MEASURES, we do not need to
worry about FINAL for now.)
So question is whether we should support RUNNING keyword.
Even if RUNNING keyword support is lacking, current patch effectively
supports RUNNING semantics with row pattern navigation (according to
the standard, the default is RUNNING). So supporting RUNNING keyword
gives users only minor benefit, for example in migration from other
DBMSs that use the RUNNING keyword in the target system. In my
opinion, the effort to add support for the RUNNING keyword is not
worth the trouble. Thoughts?
Regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2026-09-26 11:54:25 | Re: Several issues with postgres_fdw stats import |
| Previous Message | Enrique Sánchez | 2026-09-26 11:32:00 | Re: Extended statistics improvement: multi-column MCV missing values |