Hi,

Currently, any OOM triggered within getNotify and getParameterStatus
will drop the connection and set error_result=true.

However, this error is currently ignored in 2 spots:
getCopyDataMessage and pqFunctionCall3. They will continue to process
the dead connection without reporting the error.

The attached patch fixes the issue by returning the error (-2 for
getCopyDataMessage, the PGresult for pqFunctionCall3) whenever a fatal
error was triggered.

Regards,
Anthonin Bonnefoy

Attachment: v1-0001-Fix-error-handling-in-getCopyDataMessage-and-pqFu.patch
Description: Binary data

Reply via email to