Re: LDAP authenticated session terminated by signal 11: Segmentation fault, PostgresSQL server terminates other active server processes - Mailing list pgsql-general

From Tom Lane
Subject Re: LDAP authenticated session terminated by signal 11: Segmentation fault, PostgresSQL server terminates other active server processes
Date
Msg-id 6823.1551193055@sss.pgh.pa.us
Whole thread Raw
In response to Re: LDAP authenticated session terminated by signal 11: Segmentationfault, PostgresSQL server terminates other active server processes  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: LDAP authenticated session terminated by signal 11: Segmentationfault, PostgresSQL server terminates other active server processes
List pgsql-general
Thomas Munro <thomas.munro@gmail.com> writes:
> Question
> for the list: other stuff in the server needs libpthread (SSL, LLVM,
> ...), so why are we insisting on using non-MT LDAP?

The traditional reason for avoiding that is the risk of a server
process becoming multi-threaded.  There are live bugs of that ilk
on Darwin, and we actually have cross-checks for the case in our
code (see HAVE_PTHREAD_IS_THREADED_NP stanzas).

If pthread_is_threaded_np(), or something equivalent, is widely available
then it might be all right to try solving this going forward by switching
to libldap_r and seeing if anyone hits those cross-checks.  I'd be afraid
to risk it in the back branches though ...

            regards, tom lane


pgsql-general by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Channel binding not supported using scram-sha-256 passwords
Next
From: Tom Lane
Date:
Subject: Re: Channel binding not supported using scram-sha-256 passwords