From: Etsuro Fujita <efujita@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: postgres_fdw: Fix handling of a pending asynchronous request in
Date: Thu, 27 Jan 2022 07:23:27 +0000
Message-ID: <E1nCz7v-0007fO-RL@gemulon.postgresql.org> (raw)
postgres_fdw: Fix handling of a pending asynchronous request in postgresReScanForeignScan().
Commit 27e1f1456 failed to process a pending asynchronous request made
for a given ForeignScan node in postgresReScanForeignScan() (if any) in
cases where we would only reset the next_tuple counter in that function,
contradicting the assumption that there should be no pending
asynchronous requests that have been made for async-capable subplans for
the parent Append node after ReScan. This led to an assert failure in
an assert-enabled build. I think this would also lead to mis-rewinding
the cursor in that function in the case where we have already fetched
one batch for the ForeignScan node and the asynchronous request has been
made for the second batch, because even in that case we would just reset
the counter when called from that function, so we would fail to execute
MOVE BACKWARD ALL.
To fix, modify that function to process the asynchronous request before
restarting the scan.
While at it, add a comment to a function to match other places.
Per bug #17344 from Alexander Lakhin. Back-patch to v14 where the
aforesaid commit came in.
Patch by me. Test case by Alexander Lakhin, adjusted by me. Reviewed
and tested by Alexander Lakhin and Dmitry Dolgov.
Discussion: https://postgr.es/m/17344-226b78b00de73a7e@postgresql.org
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/9e283fc85d66f6e4d355c6996e863afb026866d4
Modified Files
--------------
contrib/postgres_fdw/expected/postgres_fdw.out | 37 ++++++++++++++++++++++++++
contrib/postgres_fdw/postgres_fdw.c | 14 ++++++++++
contrib/postgres_fdw/sql/postgres_fdw.sql | 17 ++++++++++++
3 files changed, 68 insertions(+)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: efujita@postgresql.org
Subject: Re: pgsql: postgres_fdw: Fix handling of a pending asynchronous request in
In-Reply-To: <E1nCz7v-0007fO-RL@gemulon.postgresql.org>
References: <E1nCz7v-0007fO-RL@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox