From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Simplifying replication |
Date: | 2010-10-19 18:20:25 |
Message-ID: | 4CBDE169.4060008@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greg,
> The way things stand you *always* need archived logs. Even if you have
> streaming set up it might try to use archived logs if it falls too far
> behind.
Actually, you don't. If you're willing to accept possible
desynchronization and recloning of the standbys, then you can skip the
archive logs.
> Timelines are not as obvious but perhaps that's our own mistake. When
> you fail over to your replica shouldn't the new master get a new
> timelineid? Isn't that the answer to the failure case when a slave
> finds it's ahead of the master? If it has already replayed logs from a
> different timelineid in the same lsn range then it can't switch
> timelines to follow the new master. But if it hasn't then it can.
Oh? Do we have this information (i.e. what LSNs are associated with
which timeline)?
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-10-19 18:52:01 | Re: Creation of temporary tables on read-only standby servers |
Previous Message | Greg Stark | 2010-10-19 18:12:16 | Re: Simplifying replication |