| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | assam258(at)gmail(dot)com |
| Cc: | jian(dot)universality(at)gmail(dot)com, 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-20 07:47:15 |
| Message-ID: | 20260920.164715.1010057096268092802.ishii@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Henson,
> As things stand, neither shape is giving a wrong answer. They just
> take longer than they need to. That is an optimization we have not
> done rather than a defect, and the current series is about defects, so
> I would rather push the fix down the list.
>
> What do you think?
I agree. IMO stabilizing our code is the first priority. We can
tackle the optimization later (probably after the first version of
RPR gets committed).
Also I think we should add this to the RPR restriction list to be
fair for those who are willing to evaluate/review RPR patches.
- Pushing down a run condition is disabled if DEFINE clause exists.
- Replacing frame options by support functions is disabled if DEFINE
clause exists.
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 | Alexandre Felipe | 2026-09-20 07:50:08 | Re: pg_regress: schedule multi-line test groups |
| Previous Message | Bharath Rupireddy | 2026-09-20 04:54:00 | Re: [PATCH] Release replication slot on error in SQL-callable slot functions |