| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Abhijit Menon-Sen <ams(at)toroid(dot)org>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Naming of gss_accept_deleg |
| Date: | 2023-05-22 13:42:44 |
| Message-ID: | 593432.1684762964@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> I noticed that the value that enables this feature at libpq client side
> is 'enable'. However, for other Boolean settings like sslsni,
> keepalives, requiressl, sslcompression, the value that enables feature
> is '1' -- we use strings only for "enum" type of settings.
> Also, it looks like connectOptions2() doesn't validate the string value.
Hmm, it certainly seems like this ought to accept exactly the
same inputs as other libpq boolean settings. I can take a look
unless somebody else is already on it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Abhijit Menon-Sen | 2023-05-22 13:44:40 | Re: Naming of gss_accept_deleg |
| Previous Message | Aleksander Alekseev | 2023-05-22 13:19:48 | Re: "38.10.10. Shared Memory and LWLocks" may require a clarification |