Re: PQexec() hangs on OOM

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: PQexec() hangs on OOM
Date: 2015-09-07 15:13:15
Message-ID: CAB7nPqTZ4PcYdHfaKUUJfydU5p260bjmghiTu=adwAzZFZCRzA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 Content-Type Size
extended.c text/x-csrc 1.1 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2015-09-08 11:48:38 Re: PQexec() hangs on OOM
Previous Message Michael Paquier 2015-09-07 13:41:34 Re: PQexec() hangs on OOM