Re: Update LDAP Protocol in fe-connect.c to v3

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Andrew Jackson <andrewjackson947(at)gmail(dot)com>
Cc: Pavel Seleznev <pavel(dot)seleznev(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Update LDAP Protocol in fe-connect.c to v3
Date: 2025-08-12 15:36:52
Message-ID: 7d03a2c7-1d49-4cbb-86b6-79facc7cd036@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 23.05.25 13:51, Peter Eisentraut wrote:
> On 15.05.25 14:54, Pavel Seleznev wrote:
>> I applied your patch. I ran extended application tests relative to
>> vanilla ones, which include various scenarios of working with LDAP and
>> I think that we can safely apply the patch in the PG18.
>>
>> I did not see the need for additional LDAP tests, since compatibility
>> is provided by the LDAP library itself,  and not by the Postgres code.
>> Also  protocol version 3 has been published for quite a long time
>> (more than 20 years) and real use by clients is through version 3
>
> FWIW, I'm prepared to commit this, but not for PG 18 at this point.

I have looked at this patch again. There is a CI failure on Windows,
and I was also able to reproduce this in my own CI runs, so it's not
just a fluke.

https://cirrus-ci.com/task/6576976439279616?logs=build#L1271

The whole thing is puzzling, since we use the same code in the backend,
without any Windows-specific guards. No clue.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2025-08-12 15:42:48 Re: Adding locks statistics
Previous Message Tomas Vondra 2025-08-12 15:06:50 Re: Adding basic NUMA awareness