Skip site navigation (1) Skip section navigation (2)

Re: Simplifying replication

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: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

> 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.

In response to


pgsql-hackers by date

Next:From: Robert HaasDate: 2010-10-19 18:52:01
Subject: Re: Creation of temporary tables on read-only standby servers
Previous:From: Greg StarkDate: 2010-10-19 18:12:16
Subject: Re: Simplifying replication

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group