Re: LDAP authentication fails with concurrent create extensions

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Greg k <gregg(dot)kay(at)gmail(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: LDAP authentication fails with concurrent create extensions
Date: 2018-04-20 02:09:55
Message-ID: CAEepm=28p9cTp=WJD00OyT6yuGJGTokuQhXR29jXA++YyjwQ2w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Apr 20, 2018 at 1:43 PM, Greg k <gregg(dot)kay(at)gmail(dot)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.

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Munro 2018-04-20 02:27:45 Re: LDAP authentication fails with concurrent create extensions
Previous Message Greg k 2018-04-20 01:43:34 Re: LDAP authentication fails with concurrent create extensions