Re: Missing compiled default for channel_binding param from PQconndefaults

From: Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Missing compiled default for channel_binding param from PQconndefaults
Date: 2020-12-28 03:04:46
Message-ID: CA+mi_8aeDXE2Q0xX4PCq+iO_RfZKqcsDgpaC-dpv5Y+MT1zSYA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, 28 Dec 2020 at 03:00, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> I wrote:
> > If the null parameter gets passed through cleanly, why don't we end
> > up with connectOptions2 inserting the correct value (line 1257 as
> > of HEAD)?
>
> Oh, wait, I misunderstood your original complaint. It's not that
> connections are failing, it's just that you would like PQconndefaults
> to make the default value visible if there is one, right?

Yes, I was about to reply exactly that :) I've only found a
discrepancy between PQconninfo(pgconn) and PQconndefaults(), not a
connection problem

Cheers

-- Daniele

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-12-28 06:41:47 BUG #16793: Libxml2 contains a null pointer dereference flaw in xpath.c
Previous Message Tom Lane 2020-12-28 03:00:50 Re: Missing compiled default for channel_binding param from PQconndefaults