Re: LDAP authentication fails with concurrent create extensions - Mailing list pgsql-bugs

From Thomas Munro
Subject Re: LDAP authentication fails with concurrent create extensions
Date
Msg-id CAEepm=0YiMV-Orprr8btb1b+hpjJfTO=UyNvtBfLrXLARzBvfQ@mail.gmail.com
Whole thread Raw
In response to Re: LDAP authentication fails with concurrent create extensions  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-bugs
On Fri, Apr 20, 2018 at 2:09 PM, Thomas Munro
<thomas.munro@enterprisedb.com> wrote:
> On Fri, Apr 20, 2018 at 1:43 PM, Greg k <gregg.kay@gmail.com> wrote:
>> Do I need to raise this as an issue or bug?
>
> It seems like we might need a patch on that adds ldap_set_option(ldap,
> LDAP_OPT_RESTART, LDAP_OPT_ON) somewhere in auth.c to tell it to
> restart on EINTR.

I'm a bit confused about that; how are you supposed to do that early
enough to cover all its syscalls if you don't have the handle until
after you've connected?  Perhaps CheckLDAPAuth() (or higher up) should
be blocking signals instead, or at least SIGUSR1 (I guess that's what
you're receiving -- can you tell?)

-- 
Thomas Munro
http://www.enterprisedb.com


pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: LDAP authentication fails with concurrent create extensions
Next
From: PG Bug reporting form
Date:
Subject: BUG #15163: Unable to get the OpenGPG data