On 06/21/2014 12:52 PM, Craig Ringer wrote:
>
>> Oops, it's my mistake. It may be better to rewrite the code completely
>> using libpq APIs instead of ODBC APIs.
>
> I don't know if that'll work.
... and in fact there are more issues, too.
If the DSN is using SSPI, MSDTC.exe probably won't be able to
authenticate to the DB as them. Same with any other kind of connection
that depends on the properties of the current user account.
Meh.
Given the low uptake of MSDTC and XA with Pg I think a lot of this can
just be documented away - "don't do that". So I'm not going to go
charging around trying to find 100% perfect solutions at the expense of
"good enough for the real world".
Where possible I'd like to find ways to produce useful errors though,
preferably at transaction enlistment time rather than commit phase II.
Suggestions would be valued.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
