> I think that this case would often happen. So, we should establish a certain
> solution or procedure to the case where TLI of the master doesn't match
> TLI of the slave. If we only allow the case where TLI of both servers is the
> same, the configuration after failover always needs to get the base backup
> on the new master. It's unacceptable for many users. But, I think that it's
> the role of admin or external tools to copy history files to the slave from
> the master.
Hmm. There's more problems than the TLI with that. For the original
master to catch up by replaying WAL from the new slave, without
restoring from a full backup, the original master must not write to disk
*any* WAL that hasn't made it to the slave yet. That is certainly not
true for asynchronous replication, but it also throws off the idea of
flushing the WAL concurrently to the local disk and to the slave in
synchronous mode.
I agree that having to get a new base backup to get the old master catch
up with the new master sucks, so I hope someone sees a way around that.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
No comments:
Post a Comment