Ahmed wrote
>
> Hi,
>
> In my email, I mistakenly assumed that the next version would be 2.0.12.0,
> which was not. My bad.
>
> I checked the source and confirmed that the 2.0.11.0 has the bug, and the
> immediate next version (2.0.11.91) has the fix. You can use the version
> 2.0.11.92
> <http://pgfoundry.org/frs/?group_id=1000140&release_id=1889>,
> which is the latest stable release.
>
>
> -Ahmed
>
*@Ahmed -* Thank you so much. I just ran a quick test and everything looks
like it's going to work great. I was really going to have to start pulling
my hair out over that one if it didn't work.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/could-not-accept-SSPI-security-context-tp3275102p5166312.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.