Re: BUG #16330: psql accesses null pointer in connect.c:do_connect

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, hghwng(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16330: psql accesses null pointer in connect.c:do_connect
Date: 2020-03-31 13:43:36
Message-ID: 2589.1585662216@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael Paquier <michael(at)paquier(dot)xyz> writes:
> On Mon, Mar 30, 2020 at 12:48:51PM -0300, Alvaro Herrera wrote:
>> On 2020-Mar-30, Tom Lane wrote:
>>> I wonder if we should force reuse_previous to false if there's
>>> no o_conn, rather than fixing this stuff piecemeal.

>> That was my impression too.

> Good point. What do you think about the attached then?

WFM.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2020-03-31 13:52:59 Re: BUG #16330: psql accesses null pointer in connect.c:do_connect
Previous Message Amit Langote 2020-03-31 09:37:56 Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006