|Subject||Re: Transaction IDs|
> So, during DB running time, there would not be same transaction ids ?dependency we
> I thought, that to uniquely correctly identify current sql
> have to use composite key : current_connection + current_transaction.If transaction ids repeated themselves, then garbage collection would
be in a lot of trouble, as would the whole multi version record thing.
Every transaction gets the next ID.
But you cant really use it for anything with long term significance,
as a backup-restore cycle resets it back to 0. Still it is helpful
information from time to time.