From: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Fix calloc check if oom (PQcancelCreate) |
Date: | 2024-05-27 14:06:30 |
Message-ID: | CAEudQAoxwuyBVMGG5PPpjddpeLgK8tFVu==OgMWk_DqhmSnjZA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Daniel,
Em seg., 27 de mai. de 2024 às 10:23, Daniel Gustafsson <daniel(at)yesql(dot)se>
escreveu:
> > On 27 May 2024, at 14:25, Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> wrote:
>
> > I think that commit 61461a3, left some oversight.
> > The function *PQcancelCreate* fails in check,
> > return of *calloc* function.
> >
> > Trivial fix is attached.
>
> Agreed, this looks like a copy/paste from the calloc calls a few lines up.
>
Yeah.
>
> > But, IMO, I think that has more problems.
> > If any allocation fails, all allocations must be cleared.
> > Or is the current behavior acceptable?
>
> Since this is frontend library code I think we should free all the
> allocations
> in case of OOM.
>
Agreed.
With v1 patch, it is handled.
best regards,
Ranier Vilela
Attachment | Content-Type | Size |
---|---|---|
v1-fix-calloc-check-oom-PQcancelCreate.patch | application/octet-stream | 1.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Ranier Vilela | 2024-05-27 14:31:24 | Fix use of possible uninitialized variable retval (src/pl/plpgsql/src/pl_handler.c) |
Previous Message | Alvaro Herrera | 2024-05-27 13:26:58 | Re: pgsql: Add more SQL/JSON constructor functions |