From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Michael Meskes <meskes(at)postgresql(dot)org> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: This routine was calling ecpg_alloc to allocate to memory but di |
Date: | 2015-08-12 12:28:03 |
Message-ID: | CAB7nPqRcCz_NEGxF9dwMstdP41JhVM1RSO8Dxb3_vCUXVWVOwA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On Wed, Aug 12, 2015 at 8:59 PM, Michael Meskes <meskes(at)postgresql(dot)org> wrote:
> On 23.07.2015 09:19, Michael Paquier wrote:
>> On Thu, Feb 5, 2015 at 11:14 PM, Michael Meskes <meskes(at)postgresql(dot)org> wrote:
>>> This routine was calling ecpg_alloc to allocate to memory but did not
>>> actually check the returned pointer allocated, potentially NULL which
>>> could be the result of a malloc call.
>>>
>>> Issue noted by Coverity, fixed by Michael Paquier <michael(at)otacoo(dot)com>
>>
>> Coming back to it, perhaps this meritates a backpatch? Even if that's
>> unlikely to happen...
>
> cherry-picked and pushed to all back branches.
>
> Sorry, the disadvantage of testing in master for a while, I simply
> forgot about this change.
No pb. Thanks! I forgot myself...
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2015-08-12 14:48:40 | Re: pgsql: Replace our hacked version of ax_pthread.m4 with latest upstream |
Previous Message | Michael Meskes | 2015-08-12 11:59:37 | Re: pgsql: This routine was calling ecpg_alloc to allocate to memory but di |