On Wed, Aug 26, 2026 at 7:00 AM Михаил Купцов <mr.cuptsov2018@yandex.ru> wrote:
> But if we think about it within the current state of configuration:
(We can think about it that way, but I'm not sure it makes sense to
split the difference between the current unhelpful behavior and a new
behavior that must break compatibility in some form anyway. Maybe we
could just implement the desired behavior with a clean break instead;
that's why I mentioned libpqrc.)
> The idea of the patch is to ensure that the client-side performs stricter configuration checking for CRL files than
itcurrently does.
Right, but since Daniel pointed out that this isn't a straight upgrade
in behavior, I don't think it necessarily gets the benefit of an
"incremental improvement" pass.
--Jacob