Re: pgsql: Fix handling of HBA ldapserver with multiple hostnames.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Fix handling of HBA ldapserver with multiple hostnames.
Date: 2018-11-13 14:39:45
Message-ID: 14114.1542119985@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
> On Tue, Nov 13, 2018 at 6:54 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Hm, what warnings?

> Apple ships OpenLDAP headers that tell you to ditch it and use Apple
> OpenDirectory Framework:

Oh, that. I just use -Wno-deprecated-declarations.

A bigger issue to my mind is that configure bleats about the
OpenLDAP version:

checking for compatible LDAP implementation... (cached) no
configure: WARNING:
*** With OpenLDAP versions 2.4.24 through 2.4.31, inclusive, each backend
*** process that loads libpq (via WAL receiver, dblink, or postgres_fdw) and
*** also uses LDAP will crash on exit.

I have not experimented to see if that's really true on recent macOS,
but if it is, it'd be a problem for production use.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2018-11-13 18:04:23 pgsql: Align ECPG lexer more closely with the core and psql lexers.
Previous Message Peter Eisentraut 2018-11-13 12:52:22 pgsql: doc: Fix minor whitespace issue