Re: Add RESPECT/IGNORE NULLS and FROM FIRST/LAST options
Tatsuo Ishii <ishii@postgresql.org>
From: Tatsuo Ishii <ishii@postgresql.org>
To: ojford@gmail.com, peter@eisentraut.org
Cc: li.evan.chao@gmail.com, krasiyan@gmail.com, tgl@sss.pgh.pa.us,
vik@postgresfriends.org, andrew@tao11.riddles.org.uk, david@fetter.org,
pgsql-hackers@lists.postgresql.org
Date: 2025-09-24T13:18:42Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix coding style with "else".
- 20628b62e46e 19 (unreleased) landed
-
Fix multi WinGetFuncArgInFrame/Partition calls with IGNORE NULLS.
- 2d7b247cb414 19 (unreleased) landed
-
Fix Coverity issue reported in commit 2273fa32bce.
- dd766a441d69 19 (unreleased) landed
-
Use ereport rather than elog in WinCheckAndInitializeNullTreatment.
- 5f3808646f67 19 (unreleased) landed
-
Avoid uninitialized-variable warnings from older compilers.
- 71540dcdcb22 19 (unreleased) cited
-
Fix Coverity issues reported in commit 25a30bbd423.
- 2273fa32bce7 19 (unreleased) landed
-
Improve EXPLAIN's display of window functions.
- 8b1b342544b6 18.0 cited
-
Automatically generate node support functions
- 964d01ae90c3 16.0 cited
Hi Oliver, > On Wed, Sep 24, 2025 at 6:39 AM Tatsuo Ishii <ishii@postgresql.org> wrote: > >> I tried to change all "int ignore_nulls;" to "uint8 ignore_nulls;" but >> gen_node_support.pl dislikes it and complains like: >> >> could not handle type "uint8" in struct "FuncCall" field "ignore_nulls" >> >> > uint8 was missing in one place in that perl script. The attached patch > silences it for uint8/uint16. Thank you for the patch. (I noticed int8 is also missing). I have looked into the commit 964d01ae90c3 which was made by Peter. I have quick read through the discussion to know why uint8/uint16 (and int8) are missing in gen_node_support.pl. Unfortunately I have no clear idea why these data types are missing in the script. Peter, Maybe you wanted to limit the data types that are actually used at that point? If so, probably we should only add uint8 support this time (uint8 is only needed to implement $Subject for now). What do you think? Best regards, -- Tatsuo Ishii SRA OSS K.K. English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp