Ivan Prenosil wrote:

>
> But even with read only database each transaction will get
> unique transaction id,

Actually, they don't. There's no place to store transaction ids,
so a read-only database just uses the same number over and over.

> starting with value of next transaction
> stored on database header page. That is why I think that
> value on header page should be slightly changed before backup.

If the last number is invalid, then it will have to be changed.
However, it would be very easy to fix even 1.0 and 1.5 to
recognize that the next transaction id is going to cause
problems, and set the database to be read only. I think that
would prevent catastrophes...


Best,


Ann