Re: Add ldapservice connection parameter
Andrew Jackson <andrewjackson947@gmail.com>
From: Andrew Jackson <andrewjackson947@gmail.com>
To: Andrey Borodin <x4mmm@yandex-team.ru>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>,
pgsql-hackers <pgsql-hackers@postgresql.org>, Roman Khapov <rkhapov@yandex-team.ru>, niushiji@gmail.com
Date: 2026-03-30T17:32:20Z
Lists: pgsql-hackers
Attachments
- pgservice-0002-Allow-LDAP-lookup-from-pgservice-connection-paramete.patch (text/x-patch) patch 0002
- ldapserviceurl-0005-Add-ldapservice-connection-parameter.patch (text/x-patch) patch 0005
Andrey, Thank you for the review. >I like "ldapservice" approach more. I don't like breaking changes, even for very small number of users. After thinking about it more it would be pretty easy to make this non breaking for users. The attached patch `pgservice-0002-Allow-LDAP-lookup-from-pgservice-connection-paramete.patch` implements this. Basically if the ldap connection parameter happens to already exist in pg_service, no LDAP lookup is performed, the values are instead taken from the pg_service.conf file. I'm fine with either implementation direction that is the most simple though. Also attaching the patch `ldapserviceurl-0005-Add-ldapservice-connection-parameter.patch` which addresses some issues you found with the previous patch. - renames parameter from ldapservice to ldapserviceurl - Adds a comment above the ldapserviceurl call explaining the reason for ignoring any error info besides zero/non-zero - Changes dispsize to 64. In reality it maybe should be higher but I was not comfortable changing it to something like 1024 because it was an order of magnitude larger than anything else. Just set it to the current max of 64. - Also moved the parameter definition and added comments about how it is defined even on non LDAP builds. This coincides with similar comments for SSL/GSS specific parameters, though there are no such comments left for oauth. Let me know if there is anything else you see missing. Thanks again, Andrew Jackson