Re: How come drongo didn't fail authentication here?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: How come drongo didn't fail authentication here?
Date: 2022-07-28 15:29:44
Message-ID: 57fcee8a-f8d1-f719-3213-37462e341cde@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2022-07-28 Th 10:55, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> On 2022-07-28 Th 10:24, Tom Lane wrote:
>>> How can that be? Have we somehow broken SSPI authentication
>>> in HEAD?
>> Nothing is broken. On HEAD drongo uses Unix sockets.
> I see. Seems like we've created a gotcha for ourselves:
> a test script can look perfectly fine in Unix-based testing,
> and even in Windows CI, and then fail when it hits the back
> branches in the buildfarm. Is it worth doing something to
> cause the lack of a valid auth_extra spec to fail on Unix?
>
>

Maybe we should just have a windows testing instance that doesn't use
Unix sockets at all.

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-07-28 15:39:44 Re: make update-po@master stops at pg_upgrade
Previous Message Alvaro Herrera 2022-07-28 15:23:30 Re: make update-po@master stops at pg_upgrade