From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
Cc: | Andrew Jackson <andrewjackson947(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Update LDAP Protocol in fe-connect.c to v3 |
Date: | 2025-04-03 13:42:02 |
Message-ID: | 1287955.1743687722@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
> Here is a slightly polished version of this patch. I added an error
> message, and changed the return code, but it's a bit confusing which one
> might be the right one.
I'm kind of -0.5 on declaring the variable as "const", because none of
our existing calls of ldap_set_option do that. I do see that the
Linux man page for ldap_set_option claims that that argument can be
const, but I think you're risking a portability gotcha for no large
gain. LGTM otherwise.
> My hunch right now is that we should probably take the patch that sets
> the version option and consider it for backpatching. The patch with the
> tests can be held for detailed review later.
+1 for that plan.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Srirama Kucherlapati | 2025-04-03 13:45:01 | RE: AIX support |
Previous Message | Andres Freund | 2025-04-03 13:40:49 | Re: Test to dump and restore objects left behind by regression |