Re: PQexec() hangs on OOM - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: PQexec() hangs on OOM
Date
Msg-id CAB7nPqTZ4PcYdHfaKUUJfydU5p260bjmghiTu=adwAzZFZCRzA@mail.gmail.com
Whole thread Raw
In response to Re: PQexec() hangs on OOM  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: PQexec() hangs on OOM
Re: PQexec() hangs on OOM
List pgsql-bugs
On Mon, Sep 7, 2015 at 10:41 PM, Michael Paquier wrote:
> In any case, attached are two patches:
> - 0001 adds the OOM/failure handling for the BIND and COPY start
> messages. This time the connection is not dropped. After a failure,
> successive commands work as well, this addresses the previous issue
> you reported.
> - 0002 is a cleanup bonus, getRowDescriptions and getAnotherTuple have
> some dead code that I think would be better removed, those are
> remnants from a copy/paste from the similar code of protocol 2.

And I forgot... Attached is a simple program to test BIND messages.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: PQexec() hangs on OOM
Next
From: Michael Paquier
Date:
Subject: Re: PQexec() hangs on OOM