From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniele Varrazzo <daniele.varrazzo@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Missing compiled default for channel_binding param from PQconndefaults
Date: Sun, 27 Dec 2020 21:44:52 -0500
Message-ID: <1539117.1609123492@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+mi_8biWq8rH5W4V9vXKsSAhfGQ4g8EA+2rHJFNoxT9S9ybHQ@mail.gmail.com>
References: <CA+mi_8Zo8Rgn7p+6ZRY7QdDu+23ukT9AvoHNyPbgKACxwgGhZA@mail.gmail.com>
<1536871.1609120125@sss.pgh.pa.us>
<CA+mi_8biWq8rH5W4V9vXKsSAhfGQ4g8EA+2rHJFNoxT9S9ybHQ@mail.gmail.com>
Daniele Varrazzo <daniele.varrazzo@gmail.com> writes:
> On Mon, 28 Dec 2020 at 01:48, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Isn't there a psycopg3 bug here
>> too, that it's not coping with a null default sanely?
> As far as I can see, psycopg3 reports the distinction between nulls
> and empty strings ok: see the "compiled" values in this sample. Or
> maybe I didn't understand your observation?
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)? It's possible that there's more than one thing going
wrong here, but I don't really understand why the existing code is
leading to a failure.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, daniele.varrazzo@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Missing compiled default for channel_binding param from PQconndefaults
In-Reply-To: <1539117.1609123492@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox