From: | Andrew Jackson <andrewjackson947(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Update LDAP Protocol in fe-connect.c to v3 |
Date: | 2025-04-04 16:55:42 |
Message-ID: | CAKK5BkE0wOGWwZpPcVxzN6ozsjpwVRU51svpbbCfEnDZ3Xcq4Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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
>
Attachment | Content-Type | Size |
---|---|---|
v3-0001-libpq-Set-LDAP-protocol-version-3.patch | text/x-patch | 1.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitrios Apostolou | 2025-04-04 16:55:44 | Re: [PATCH v2] parallel pg_restore: avoid disk seeks when jumping short distance forward |
Previous Message | Sami Imseih | 2025-04-04 16:55:41 | Re: rename pg_log_standby_snapshot |