Yes, it is correct. Issue appers not significant at first glance.
However, if you take into account users who are trying to migrate
their apps from MSSQL or Oracle and not willing to rewrite their apps
(relying on the OLEDB driver), you discover that it is not that small
issue. The driver just cannot provide required modes due to DB
limitation.
On May 22, 2009, at 3:18 PM, Magnus Hagander <magnus@hagander.net>
wrote:
> Tom Lane wrote:
>> Konstantin Izmailov <kizmailov@gmail.com> writes:
>>> I've asked a few people at pgcon2009 about the issue of connecting
>>> users
>>> differently: some in SSIS mode, some - with password. This is
>>> still an
>>> issue: if server is configured for SSIS, there is no way to
>>> connect with
>>> password.
>>
>> Huh? The server decides which auth method to use, not the client.
>
> I think this is exactly what Konstantin is complaining about.
>
> In his scenario, different clients connecting from the same subnet (so
> they can't use different pg_hba lines) need to use different
> authentication methods. (IIRC, this is an environment coming from
> Microsoft SQL Server which does support this)
>
> I think what he's asking for is the ability for a line in the server
> to
> allow multiple authentication methods, and then for the client to be
> able to specify which one of these it uses.
>
> Konstantin, can you confirm that this was your scenario? You explained
> it to me last night, but that was several beers into the evening...
>
> //Magnus
>
>