| 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-01-23 06:27:41 |
| Message-ID: | 20250123.152741.1191357484211664332.ishii@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Hi,
> I was able to reproduce exactly the problem, with clean compile
> and --enable-cassert:
> test=# SELECT x,y,lead(y) IGNORE NULLS OVER (ORDER BY x) FROM
> (VALUES(1,NULL),(2,2),(3,NULL)) AS v(x,y);
> x | y | lead
> ---+---+------
> 1 | | 2
> 2 | 2 | 2
> 3 | | 2
> (3 rows)
>
> test=#
> Also, make check errors out at window test (without --enable-cassert it was
> passed in previous compile):
Yeah, same here.
Another possible problem is, probably the code does not work well if
there are multiple partitions. Since win_nonnulls stores currentpos in
a partition, when the partition ends, win_nonnulls needs to be
reset. Otherwise, it mistakenly represents currentpos in the previous
partition.
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 | Pavel Stehule | 2025-01-23 06:50:23 | Re: XMLDocument (SQL/XML X030) |
| Previous Message | Krasiyan Andreev | 2025-01-23 06:08:39 | Re: Add RESPECT/IGNORE NULLS and FROM FIRST/LAST options |