Re: BUG #17828: postgres_fdw leaks file descriptors on error and aborts aborted transaction in lack of fds
| От | Tom Lane |
|---|---|
| Тема | Re: BUG #17828: postgres_fdw leaks file descriptors on error and aborts aborted transaction in lack of fds |
| Дата | |
| Msg-id | 974582.1707411864@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: BUG #17828: postgres_fdw leaks file descriptors on error and aborts aborted transaction in lack of fds (Etsuro Fujita <etsuro.fujita@gmail.com>) |
| Ответы |
Re: BUG #17828: postgres_fdw leaks file descriptors on error and aborts aborted transaction in lack of fds
|
| Список | 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
В списке pgsql-bugs по дате отправления: