diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2024-03-27 13:39:03 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2024-03-27 13:39:03 -0400 |
commit | a94f51a7bfc9e65ce3799d8cb12945bd596c5ba8 (patch) | |
tree | 925fb83cbc33828fdfa9713f42ee2224362c2b6b /contrib/postgres_fdw/postgres_fdw.c | |
parent | f5d0e866404a249d3a87a016e3ec562ab2dc6706 (diff) | |
download | postgresql-a94f51a7bfc9e65ce3799d8cb12945bd596c5ba8.tar.gz postgresql-a94f51a7bfc9e65ce3799d8cb12945bd596c5ba8.zip |
Fix unnecessary use of moving-aggregate mode with non-moving frame.
When a plain aggregate is used as a window function, and the window
frame start is specified as UNBOUNDED PRECEDING, the frame's head
cannot move so we do not need to use moving-aggregate mode. The check
for that was put into initialize_peragg(), failing to notice that
ExecInitWindowAgg() calls that function before it's filled in
winstate->frameOptions. Since makeNode() would have zeroed the field,
this didn't provoke uninitialized-value complaints, nor would the
erroneous decision have resulted in more than a little inefficiency.
Still, it's wrong, so move the initialization of
winstate->frameOptions earlier to make it work properly.
While here, also fix a thinko in a comment. Both errors crept in in
commit a9d9acbf2 which introduced the moving-aggregate mode.
Spotted by Vallimaharajan G. Back-patch to all supported branches.
Discussion: https://postgr.es/m/18e7f2a5167.fe36253866818.977923893562469143@zohocorp.com
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions