Crash on transaction replay if log_info is on and session starts with no master

When configured with transaction_replay=true and log_info enabled, if a session started without a master and later on a master would become available the next start of a transaction would trigger a transaction migration. The transaction migration code unconditionally used the old master's name and if no master was available, the master reference was not valid.