On Sat, 10 May 2014 10:53:05 +0300, "Vlad Khorsun" <hv...@users.sourceforge.net> wrote: >> I will see if I can come up with a solution for Firebird 3 without >> needing >> RDB$TRANSACTIONS to be unprotected, but doesn't - potentially - >> degenerate >> to iterating over a list of thousands if not millions of transaction >> records when recovering a distributed transaction. > > Am i already told you about isc_database_info call ? It returns > numbers of > in-limbo transactions only.
That is not sufficient for my information needs. I need the RDB$TRANSACTION_DESCRIPTION as well to deserialize the Xid I stored in it. Of course I can also query RDB$TRANSACTIONS with RDB$TRANSACTION_STATE = 1, but in the future I may also need to know if a Xid is already committed or rolled back (although the current code doesn't do that). I could (with FB 2.5 and later) also query with RDB$TRANSACTION_DESCRIPTION = X'....' (where X'....' is the serialized Xid I am looking for) although I wonder about its performance implications. On the other hand, recovery situations should be rare so it might not be problematic at all. Mark ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
