From: Josh Berkus <josh@agliodbs.com>
To: Greg Stark <gsstark@mit.edu>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Simplifying replication
Date: Tue, 19 Oct 2010 11:20:25 -0700
Message-ID: <4CBDE169.4060008@agliodbs.com> (raw)
In-Reply-To: <AANLkTimXJ6jfeZ_jY_DJJHWYRAozeAKz3aWz15MTP_t1@mail.gmail.com>
References: <4CBCE356.2080703@agliodbs.com>
<m28w1ushwz.fsf@2ndQuadrant.fr>
<4CBDC461.3050401@agliodbs.com>
<AANLkTimXJ6jfeZ_jY_DJJHWYRAozeAKz3aWz15MTP_t1@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: josh@agliodbs.com, gsstark@mit.edu
Subject: Re: Simplifying replication
In-Reply-To: <4CBDE169.4060008@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox