I find the text in the release notes of Firebird 3 for "Extension of Transaction ID Space Limit" (http://www.firebirdsql.org/file/documentation/release_notes/html/en/3_0/rnfb30-apiods.html#rnfb30-apiods-transaclimit ) a bit low on information and a bit confusing.
Especially this is confusing: "Initially in Firebird 3.0, the transaction ID space was raised to 2^32 transactions, doubling the database up-time without backup and restore. This improvement request is about shifting that limit even further, with the introduction of 48-bit internal transaction IDs that are publicly (via the API and the MON$ tables) represented as 64-bit numbers." Is the limit now 2^32 or 2^48? Could someone take some time to rewrite this for the next release. Also what is the effect of this change (and the change "Limits Raised for Attachment and Statement IDs" below that) for the wire protocol? Does this affect the handle id of statements and transactions (if so how, as those are int32 in the protocol), or does this only affect the transaction id in a service request (eg isc_spb_rpr_list_limbo_trans), if so how, because transaction ids are always length 4 VAX encoded integers (without length prefix) in the response? Mark -- Mark Rotteveel ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
