diff options
author | Etsuro Fujita <efujita@postgresql.org> | 2021-08-02 12:45:01 +0900 |
---|---|---|
committer | Etsuro Fujita <efujita@postgresql.org> | 2021-08-02 12:45:01 +0900 |
commit | fb234086fe81fb1848934b6e1f6382611fc9ad4f (patch) | |
tree | efdef28948bf4ac7f5ec6783ac1c636535eb0f52 /contrib/postgres_fdw/postgres_fdw.c | |
parent | ec410c985e6d360f666e39be5609f3c4da5edc8f (diff) | |
download | postgresql-fb234086fe81fb1848934b6e1f6382611fc9ad4f.tar.gz postgresql-fb234086fe81fb1848934b6e1f6382611fc9ad4f.zip |
Fix oversight in commit 1ec7fca8592178281cd5cdada0f27a340fb813fc.
I failed to account for the possibility that when
ExecAppendAsyncEventWait() notifies multiple async-capable nodes using
postgres_fdw, a preceding node might invoke process_pending_request() to
process a pending asynchronous request made by a succeeding node. In
that case the succeeding node should produce a tuple to return to the
parent Append node from tuples fetched by process_pending_request() when
notified. Repair.
Per buildfarm via Michael Paquier. Back-patch to v14, like the previous
commit.
Thanks to Tom Lane for testing.
Discussion: https://postgr.es/m/YQP0UPT8KmPiHTMs%40paquier.xyz
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
-rw-r--r-- | contrib/postgres_fdw/postgres_fdw.c | 22 |
1 files changed, 18 insertions, 4 deletions
diff --git a/contrib/postgres_fdw/postgres_fdw.c b/contrib/postgres_fdw/postgres_fdw.c index bd8fda9e91c..3bdf7ab1828 100644 --- a/contrib/postgres_fdw/postgres_fdw.c +++ b/contrib/postgres_fdw/postgres_fdw.c @@ -6896,12 +6896,26 @@ postgresForeignAsyncNotify(AsyncRequest *areq) ForeignScanState *node = (ForeignScanState *) areq->requestee; PgFdwScanState *fsstate = (PgFdwScanState *) node->fdw_state; - /* The request should be currently in-process */ - Assert(fsstate->conn_state->pendingAreq == areq); - /* The core code would have initialized the callback_pending flag */ Assert(!areq->callback_pending); + /* + * If process_pending_request() has been invoked on the given request + * before we get here, we might have some tuples already; in which case + * produce the next tuple + */ + if (fsstate->next_tuple < fsstate->num_tuples) + { + produce_tuple_asynchronously(areq, true); + return; + } + + /* We must have run out of tuples */ + Assert(fsstate->next_tuple >= fsstate->num_tuples); + + /* The request should be currently in-process */ + Assert(fsstate->conn_state->pendingAreq == areq); + /* On error, report the original query, not the FETCH. */ if (!PQconsumeInput(fsstate->conn)) pgfdw_report_error(ERROR, NULL, fsstate->conn, false, fsstate->query); @@ -7027,7 +7041,7 @@ process_pending_request(AsyncRequest *areq) /* * If we didn't get any tuples, must be end of data; complete the request * now. Otherwise, we postpone completing the request until we are called - * from postgresForeignAsyncConfigureWait(). + * from postgresForeignAsyncConfigureWait()/postgresForeignAsyncNotify(). */ if (fsstate->next_tuple >= fsstate->num_tuples) { |