> -----Original Message----- > From: Mark Rotteveel [mailto:m...@lawinegevaar.nl] > Sent: Martes, 06 de Mayo de 2014 15:41 > > After successfully recovering a transaction that way, the current > implementation in Jaybird deletes the entry in RDB$TRANSACTIONS > (probably as a form of house-keeping, or maybe at implementation time > the meaning of RDB$TRANSACTION_STATE was unclear). With the recent > changes to disallow access to the system tables this last > step no longer > works.
Allowing access is easy. However, this is not the main issue. We need to understand how and when this table is cleaned. The only utility READING (not writing) rdb$transactions is gfix. Since gbak doesn't use rdb$transactions, we can conclude that after a backup and restore cycle, the information is gone. I think your two questions below can be answered only by Jim or Ann: > This leads me to the questions: > 1) When are prepared or rolled back transactions removed from > RDB$TRANSACTIONS? Or are they kept indefinitely? > 2) Is there an alternative to removing this information? C. ------------------------------------------------------------------------------ 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
