aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.c
diff options
context:
space:
mode:
authorEtsuro Fujita <efujita@postgresql.org>2021-06-07 12:45:00 +0900
committerEtsuro Fujita <efujita@postgresql.org>2021-06-07 12:45:00 +0900
commitf3baaf28a6da588987b94a05a725894805c3eae9 (patch)
tree75687ca3a9446c0335a3a849ca619e5208cfb5dc /contrib/postgres_fdw/postgres_fdw.c
parenta65e9f3f1405b786673feec131879843432bf9a6 (diff)
downloadpostgresql-f3baaf28a6da588987b94a05a725894805c3eae9.tar.gz
postgresql-f3baaf28a6da588987b94a05a725894805c3eae9.zip
Fix rescanning of async-aware Append nodes.
In cases where run-time pruning isn't required, the synchronous and asynchronous subplans for an async-aware Append node determined using classify_matching_subplans() should be re-used when rescanning the node, but the previous code re-determined them using that function repeatedly each time when rescanning the node, leading to incorrect results in a normal build and an Assert failure in an Assert-enabled build as that function doesn't assume that it's called repeatedly in such cases. Fix the code as mentioned above. My oversight in commit 27e1f1456. While at it, initialize async-related pointers/variables to NULL/zero explicitly in ExecInitAppend() and ExecReScanAppend(), just to be sure. (The variables would have been set to zero before we get to the latter function, but let's do so.) Reviewed-by: Kyotaro Horiguchi Discussion: https://postgr.es/m/CAPmGK16Q4B2_KY%2BJH7rb7wQbw54AUprp7TMekGTd2T1B62yysQ%40mail.gmail.com
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions