Re: BUG #17186: In connect.c, the lock connections_mutex is not correctly released(Line 463) at the return(Line 522) - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #17186: In connect.c, the lock connections_mutex is not correctly released(Line 463) at the return(Line 522)
Date
Msg-id YTsELsxLaslKcn+m@paquier.xyz
Whole thread Raw
In response to BUG #17186: In connect.c, the lock connections_mutex is not correctly released(Line 463) at the return(Line 522)  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #17186: In connect.c, the lock connections_mutex is not correctly released(Line 463) at the return(Line 522)  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
On Fri, Sep 10, 2021 at 04:29:36AM +0000, PG Bug reporting form wrote:
> The problem is that the lock connections_mutex should be released at the end
> of the function. But it not released when conn_keywords == NULL ||
> conn_values == NULL (ecpg_alloc got errors and return NULL).

ecpg_alloc() is just a wrapper to calloc(), so errors are very
unlikely going to happen in this code path.  It does not change the
fact that it is wrong.  Nice catch, will fix.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #17186: In connect.c, the lock connections_mutex is not correctly released(Line 463) at the return(Line 522)
Next
From: PG Bug reporting form
Date:
Subject: BUG #17187: Incorrect field update operation?