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: Etsuro Fujita <etsuro.fujita@gmail.com>
Cc: Alexander Lakhin <exclusion@gmail.com>, pgsql-bugs@lists.postgresql.org
Date: 2024-02-08T17:04:24Z
Lists: pgsql-bugs
Etsuro Fujita <etsuro.fujita@gmail.com> writes: > IIUC I think the assertion failure was caused by an > error-during-error-recovery loop caused by the "epoll_create1 failed: > Too many open files" error raised in WaitLatchOrSocket called from > pgfdw_get_cleanup_result, which is called during abort cleanup. I > think a simple fix to avoid such a loop is to modify the PG_CATCH > block in pgfdw_get_cleanup_result so that it just ignores the passed > error, not re-throwing it, and restores InterruptHoldoffCount and the > memory context, like the attached. In the patch I also modified > callers of pgfdw_get_cleanup_result to issue a warning when ignoring > the error. I might be missing something, though. I do not think ignoring the passed error is *ever* acceptable. You have no idea what the error condition is or whether your hack is sufficient to recover from it. 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