Re: BUG #17083: [PATCH] PostgreSQL fails to build with OpenLDAP 2.5.x

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Adrian Ho <ml+postgresql(at)03s(dot)net>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17083: [PATCH] PostgreSQL fails to build with OpenLDAP 2.5.x
Date: 2021-07-09 02:25:03
Message-ID: YOezfzxbrMNMwoRg@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Jul 08, 2021 at 10:02:30PM +0200, Daniel Gustafsson wrote:
> On 8 Jul 2021, at 21:55, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> That being the case, I think we might be okay just going with the
>> solution in Adrian's last patch, ie use libldap_r if it's there
>> and otherwise assume that libldap is thread-safe. It looks
>> fairly unlikely that anyone will ever have an issue with that;
>> while if we complicate the configure probe, we might be introducing
>> new problems just from that.
>
> Absolutely, in light of that I agree that's the best option.

+1.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Yuetsuro Kobayashi 2021-07-09 04:12:02 Re: BUG #17089: "ERROR: invalid memory alloc request size ..." occurs when updating a fixed number of records
Previous Message Tom Lane 2021-07-08 21:42:05 Re: BUG #17095: ./configure fails thread_test.c when run under TSAN