Re: Update LDAP Protocol in fe-connect.c to v3 - Mailing list pgsql-hackers

From Andrew Jackson
Subject Re: Update LDAP Protocol in fe-connect.c to v3
Date
Msg-id CAKK5BkE0wOGWwZpPcVxzN6ozsjpwVRU51svpbbCfEnDZ3Xcq4Q@mail.gmail.com
Whole thread Raw
In response to Re: Update LDAP Protocol in fe-connect.c to v3  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Here is the same patch as v2 but with "const" removed in case you want to move forward with that change. Tested locally against the tests I wrote in the other patch to sanity check the change.

On Thu, Apr 3, 2025 at 8:42 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Peter Eisentraut <peter@eisentraut.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
Attachment

pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: rename pg_log_standby_snapshot
Next
From: Dimitrios Apostolou
Date:
Subject: Re: [PATCH v2] parallel pg_restore: avoid disk seeks when jumping short distance forward