database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-11 20:28:21 +03:00
Code Activity

Fix bogus coding in ExecAppendAsyncEventWait().

Browse Source 
No configured-by-FDW events would result in "return" directly out of a
PG_TRY block, making the exception stack dangling.  Repair.

Oversight in commit 501cfd07d; back-patch to v14, like that commit, but
as we do not have this issue in HEAD (cf. commit 50c67c201), no need to
apply this patch to it.

In passing, improve a comment about the handling of in-process requests
in a postgres_fdw.c function called from this function.

Alexander Pyhalov, with comment adjustment/improvement by me.

Discussion: https://postgr.es/m/425fa29a429b21b0332737c42a4fdc70%40postgrespro.ru
This commit is contained in:
Etsuro Fujita
2024-04-04 17:25:02 +09:00
parent c2faf48fa3
commit 3f96d113ff
2 changed files with 25 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
contrib/postgres_fdw/postgres_fdw.c
View File

@ -6968,14 +6968,16 @@ postgresForeignAsyncConfigureWait(AsyncRequest *areq)
{
/*
* This is the case when the in-process request was made by another
* Append. Note that it might be useless to process the request,
* because the query might not need tuples from that Append anymore.
* If there are any child subplans of the same parent that are ready
* for new requests, skip the given request. Likewise, if there are
* any configured events other than the postmaster death event, skip
* it. Otherwise, process the in-process request, then begin a fetch
* to configure the event below, because we might otherwise end up
* with no configured events other than the postmaster death event.
* Append. Note that it might be useless to process the request made
* by that Append, because the query might not need tuples from that
* Append anymore; so we avoid processing it to begin a fetch for the
* given request if possible. If there are any child subplans of the
* same parent that are ready for new requests, skip the given
* request. Likewise, if there are any configured events other than
* the postmaster death event, skip it. Otherwise, process the
* in-process request, then begin a fetch to configure the event
* below, because we might otherwise end up with no configured events
* other than the postmaster death event.
*/
if (!bms_is_empty(requestor->as_needrequest))
return;