On Thu, Jun 19, 2014 at 01:01:34PM -0400, Tom Lane wrote:
Noah Misch n...@leadboat.com writes:
On Thu, Jun 12, 2014 at 05:02:19PM -0400, Noah Misch wrote:
You can cause the at-exit crash by building PostgreSQL against OpenLDAP
2.4.31, connecting with LDAP authentication, and issuing LOAD
On Thu, Jun 12, 2014 at 05:02:19PM -0400, Noah Misch wrote:
You can cause the at-exit crash by building PostgreSQL against OpenLDAP
2.4.31, connecting with LDAP authentication, and issuing LOAD 'dblink'.
4. Detect older OpenLDAP versions at runtime, just before we would otherwise
initialize
Noah Misch n...@leadboat.com writes:
On Thu, Jun 12, 2014 at 05:02:19PM -0400, Noah Misch wrote:
You can cause the at-exit crash by building PostgreSQL against OpenLDAP
2.4.31, connecting with LDAP authentication, and issuing LOAD 'dblink'.
4. Detect older OpenLDAP versions at runtime, just
With LDAP support enabled, we link the backend with libldap, and we link libpq
with libldap_r. Modules like dblink and postgres_fdw link to libpq, so
loading them results in a backend having both libldap and libdap_r loaded.
Those libraries export the same symbols, and the load order rule gives
