| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Abhishek Chanda <abhishek(dot)becs(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Adding support for SSLKEYLOGFILE in the frontend |
| Date: | 2025-03-13 18:31:24 |
| Message-ID: | 2828206.1741890684@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> writes:
> Adding the PG prefix to the envvar name addresses my collision
> concern, but I think Tom's comment upthread [1] was saying that we
> should not provide any envvar at all:
>> I think it might be safer if we only accepted it as a connection
>> parameter and not via an environment variable.
> Is the addition of the PG prefix enough to address that concern too?
Indeed, I was advocating for *no* environment variable. The PG prefix
does not comfort me.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2025-03-13 19:54:46 | Re: dblink: Add SCRAM pass-through authentication |
| Previous Message | Tom Lane | 2025-03-13 18:29:20 | Re: SQLFunctionCache and generic plans |