Re: BUG #16330: psql accesses null pointer in connect.c:do_connect - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #16330: psql accesses null pointer in connect.c:do_connect
Date
Msg-id 17009.1585582541@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #16330: psql accesses null pointer in connect.c:do_connect  (Michael Paquier <michael@paquier.xyz>)
Responses Re: BUG #16330: psql accesses null pointer in connect.c:do_connect
List pgsql-bugs
Michael Paquier <michael@paquier.xyz> writes:
> On Mon, Mar 30, 2020 at 02:20:48AM +0000, PG Bug reporting form wrote:
>> If the connection to postmaster is closed, then trying to re-connect to
>> another one leads to SIGSEGV.

> A fix like the attached should be sufficient as if we know that
> PQhost() is NULL for the old connection we cannot use the old
> hostaddr.  Alvaro, what do you think?

It looks to me like there's a similar hazard a bit further down
(line 3029):

        appendConnStrVal(&connstr, PQdb(o_conn));

I wonder if we should force reuse_previous to false if there's
no o_conn, rather than fixing this stuff piecemeal.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Francisco Olarte
Date:
Subject: Re: BUG #16321: Memory leaks in PostmasterMain
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #16330: psql accesses null pointer in connect.c:do_connect