| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | heath(dot)lord(at)crunchydata(dot)com |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Jacob Champion <jchampion(at)timescale(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17625: In PG15 PQsslAttribute returns different values than PG14 when SSL is not in use for the connection |
| Date: | 2022-09-29 20:16:31 |
| Message-ID: | 360379.1664482591@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
I wrote:
> AFAICS that behavioral change is deliberate: for the single case
> of inquiring about "library", PQsslAttribute now tells you which
> SSL implementation libpq *can* use, not which one it's actually
> using on a given connection. I'm not sure that this is a great
> definition, since it's so unlike the behavior for other attributes.
Actually, wait a minute: both the documentation and the commit
message claim the new behavior is something different than what it
actually is. The intention seems to have been to change the
behavior only for the conn == NULL case. So maybe we need to
fix it as attached. This'd still be broken for the
multiple-libraries scenario, but I admit that that's pretty
hypothetical.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| fix-broken-PQsslAttribute.patch | text/x-diff | 730 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heath Lord | 2022-09-29 20:21:59 | Re: BUG #17625: In PG15 PQsslAttribute returns different values than PG14 when SSL is not in use for the connection |
| Previous Message | Tom Lane | 2022-09-29 19:58:02 | Re: [Bug][Ver 11]: Generic query plan selected is worse than custom query plan |