a native application of ours is based on distributed transactions and thus
requires all databases to provide an XA interface so that an XA-compliant
DTM (e.g. Tuxedo) can do its work.
I read in the JDBC driver FAQ (I'm not interested in the JDBC driver itself)
at http://jdbc.postgresql.org/documentation/faq.html that XA Support for the
database is scheduled for 8.1, does that still hold true (if yes, do you
have an early 8.1 ETA)?
From my understanding, supporting XA would mean to
- provide an XA library implementing the XA interface
as described in the X/Open XA specification at
- support commit preparation (the process of persisting
transactional changes without actually committing the
transaction so that a later commit is guaranteed to
succeed should the log be available in a consistent
- [optional] allow a Point-In-Time Recovery (PITR) based
on an XA XID rather than an internal transaction id or
time specification. This functionality would enable
a consistent recovery of multiple, cooperating
Judging from a one day old CVS checkout, neither of these aspects have been
addressed at this time or are currently being worked on. If at all possible,
please provide me with an update on the current status and plan on
implementing XA support. Can you estimate the time (e.g. in man-days) and
implementation complexity of integrating this functionality?
Thanks in advance for any insights in this respect!
P.S.: The 8.0 release candidate rocks, PITR works flawlessly, without a
hitch. Thanks for your efforts!
pgsql-general by date
|Next:||From: Greg Stark||Date: 2004-12-30 05:12:39|
|Subject: Re: pg_dump and pgpool|
|Previous:||From: Eric Brown||Date: 2004-12-30 01:04:27|
|Subject: Re: debug_print_plan (pg7.4) doesn't seem to do anything |