Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id 469C01337B68
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Tue, 19 Apr 2011 06:16:29 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia,
	port 10024) with ESMTP id 51600-03 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Tue, 19 Apr 2011 09:16:11 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com
 [74.125.82.50])
	by mail.postgresql.org (Postfix) with ESMTP id 0C2381337BCC
	for <pgsql-admin@postgresql.org>; Tue, 19 Apr 2011 06:16:10 -0300 (ADT)
Received: by wwc33 with SMTP id 33so5941314wwc.19
	for <pgsql-admin@postgresql.org>; Tue, 19 Apr 2011 02:16:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:message-id:date:from:user-agent:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	bh=TyIeVGehyJgDmkXvVWbnrd2ld3d3pZXDOxj5h1+eYoc=;
	b=qKr5UI5WuOAWU5Tlo6TgDgoRBJ6HShaWr3n3jAJak6PJK/zULvCeRgYyjwVJuD8u3u
	XwXxDTKlgKgdawBRUT1J6KOtYYq84CxSgLG0unaXJMKQNfCaIgckURC/Ry2yS33W/2ad
	BvyGdwRNjcvnLwYatdbi1bSdFyn5Zn/pl38x8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:user-agent:mime-version:to:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	b=EF3UMDaLUpeARNgcoeUK3KDcqQPuImWBfOyxxaAwgZI94iIXgDHY+55Hd3R5DaIs7n
	jxm1b9TzQuHJCc+ZWoWHon7Bz2E7iMxd5b4Q3elSZFlEn3f0RcfUqsxxeNgzpYwP50rt
	3Agwzx+0glqNDNRU1tIOcPwITM0ytxzDYeUXA=
Received: by 10.227.16.98 with SMTP id n34mr1176723wba.31.1303204570245;
	Tue, 19 Apr 2011 02:16:10 -0700 (PDT)
Received: from [10.10.10.48] (89-96-231-108.ip14.fastwebnet.it
 [89.96.231.108])
	by mx.google.com with ESMTPS id y29sm3755704wbd.21.2011.04.19.02.16.09
	(version=TLSv1/SSLv3 cipher=OTHER);
	Tue, 19 Apr 2011 02:16:09 -0700 (PDT)
Message-ID: <4DAD52D8.1090006@gmail.com>
Date: Tue, 19 Apr 2011 11:16:08 +0200
From: rudi <rudolone@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Streaming replication: rsync to switchover
References: <4DAC7205.8080203@kemen.it>
	<BANLkTikrqROJjNiVpmkZorkPM7nUYHZUAw@mail.gmail.com>
In-Reply-To: <BANLkTikrqROJjNiVpmkZorkPM7nUYHZUAw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=2.421 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	FREEMAIL_FROM=0.001, FS_REPLICA=3.599, RFC_ABUSE_POST=0.001,
	SARE_SPEC_REPLICA=0.72
X-Spam-Level: **
X-Archive-Number: 201104/164
X-Sequence-Number: 37345

On 04/19/2011 10:09 AM, Gerhard Hintermayer wrote:
> assuming you have configured rsyncd on the server as:
>
> [postgresql-data]
>      uid = postgres
>      path = /var/lib/postgresql/9.0/data
>      comment = PostgreSQL 9.0 data dir
>      exclude = postmaster.log pg_xlog/* postmaster.pid postgresql.conf

So you keep the old pg_xlog ... But, what about wal that the former 
master hasn't yet sent to the slave? I wonder if the former-master could 
apply them, becoming out-of-sync with the former-slave (that never 
recevied those wal).

thanks

-- 
rudi