Re: BUG #17828: postgres_fdw leaks file descriptors on error and aborts aborted transaction in lack of fds
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Thomas Munro <thomas.munro@gmail.com>,
Etsuro Fujita <etsuro.fujita@gmail.com>,
Alexander Lakhin <exclusion@gmail.com>,
pgsql-bugs@lists.postgresql.org
Date: 2024-02-09T00:20:35Z
Lists: pgsql-bugs
Andres Freund <andres@anarazel.de> writes: > I might be missing something here, but leaving the concrete crash aside, why > is it ok for pgfdw_get_cleanup_result() etc to block during abort processing? It's not pretty, for sure. I thought briefly about postponing the cleanup until we next try to use the connection, but I fear the semantic side-effects of that would be catastrophic. We can't leave the remote's query sitting open long after the local transaction has been canceled --- that risks undetected deadlocks, at the least. I think all we can do is try to reduce the risk of failure during transaction cleanup. regards, tom lane
Commits
-
Fix resource leak when a FDW's ForeignAsyncRequest function fails
- 555276f85940 14.11 landed
- 481d7d1c01c6 15.6 landed
- 501cfd07dac6 16.2 landed