From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
---|---|
To: | krasiyan(at)gmail(dot)com |
Cc: | ojford(at)gmail(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, vik(at)postgresfriends(dot)org, pgsql-hackers(at)postgresql(dot)org, andrew(at)tao11(dot)riddles(dot)org(dot)uk, david(at)fetter(dot)org |
Subject: | Re: Add RESPECT/IGNORE NULLS and FROM FIRST/LAST options |
Date: | 2025-03-29 11:18:09 |
Message-ID: | 20250329.201809.1463386697879435538.ishii@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Hi,
> Patch applies and compiles, all included tests passed and after the latest
> fixes for non-nulls array, performance is near to lead/lag without support
> of "ignore nulls".
> I have been using the last version for more than one month in a production
> environment with real data and didn't find any bugs, so It is ready for
> committer status.
One thing I worry about the patch is, now the non-nulls array
optimization was removed. Since then I have been thinking about if
there could be other way to optimize searching for non null rows.
Best reagards,
--
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 | Ashutosh Bapat | 2025-03-29 11:54:51 | Re: Reducing memory consumed by RestrictInfo list translations in partitionwise join planning |
Previous Message | Alexander Korotkov | 2025-03-29 11:03:07 | Re: Replace IN VALUES with ANY in WHERE clauses during optimization |