From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | "Inoue, Hiroshi" <inoue(at)tpf(dot)co(dot)jp> |
Cc: | "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: XA registry entries are missing from 64-bit install |
Date: | 2014-06-12 08:28:19 |
Message-ID: | 539964A3.8090707@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
On 06/12/2014 02:02 PM, Inoue, Hiroshi wrote:
>
>
> Because msdtc process seems a 64bit application, 64bit pgxalib.dll
> should be registered even when 32bit applications use MSDTC support.
> The current way of registration isn't appropriate and 64bit installer
> would have to register the entry beforehand.
OK, so if I understand this right, it might be helpful to have
pgenlist.dll expose a function that's callable with rundll32 to create
the registry entries. Call it, say, registerxa().
Then the registry entry creation code currently in
EnlistInDtc_1pipe(...) could be factored out so it's callable as part of
EnlistInDtc_1pipe(...) or via the new entry point.
The installer can then invoke
rundll32 pgenlist.dll,registerxa
to create the appropriate entries.
Reasonable?
Or is it better to just create/update the registry entries directly
using the MSI?
Looking at the current code, it appears that it tries to overwrite any
existing value in that subkey if XA enlistment fails. So it should also
"upgrade" existing entries. Right?
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2014-06-12 08:43:04 | PATCH: WiX has moved |
Previous Message | Craig Ringer | 2014-06-12 07:53:18 | Build failure with VS 2012 due to uninitialized pointers |