Re: Cascading replication and recovery_target_timeline='latest'

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: hlinnaka(at)iki(dot)fi
Cc: pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>
Subject: Re: Cascading replication and recovery_target_timeline='latest'
Date: 2012-09-05 04:56:55
Message-ID: 1346821015.16318.1.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 2012-09-04 at 19:34 -0700, Heikki Linnakangas wrote:
> > The attached patch fixes it for me. It fixes the original problem, by
> > adding the missing locking and terminating walsenders on a target
> > timeline change, and also changes the behavior wrt. WAL segments
> > restored from the archive, as I just suggested in another email
> > (http://archives.postgresql.org/pgsql-hackers/2012-09/msg00206.php).
>
> Committed that.

New compiler warnings:

xlog.c: In function ‘XLogFileRead’:
xlog.c:2785:14: error: unused variable ‘endptr’ [-Werror=unused-variable]
xlog.c:2784:25: error: unused variable ‘xlogctl’ [-Werror=unused-variable]

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2012-09-05 05:09:24 Re: Cascading replication and recovery_target_timeline='latest'
Previous Message Tom Lane 2012-09-05 04:42:35 Re: pg_upgrade diffs on WIndows