Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1

On 2013-11-18 11:38:43 -0800, Christophe Pettus wrote:
>
> On Nov 18, 2013, at 11:28 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> > Could you detail how exactly the base backup was created? Including the
> > *exact* logic for copying?
>
> 0. Before any of this began, P1 was archiving WAL segments to AWS-S3.
> 1. pg_start_backup('', true) on P1.
> 2. Using rsync -av on P1, the entire $PGDATA directory was pushed from P1 to S2.

Without deleting any data, including pg_xlog/, backup.label, anything?

Did you have hot_standby enabled on all of those machines? Even on the
9.0.13 cluster?

> > Could you list the *exact* steps you did to startup the cluster?
>
> 0. Before any of this began, P2 was archiving WAL segments to AWS-S3.
> 1. Initial (empty) data directory deleted on S2.
> 2. New data directory created with:
>
> /usr/lib/postgresql/9.3/bin/pg_basebackup --verbose --progress --xlog-method=stream --host=<ip> --user=repluser --pgdata=/data/9.3/main
>
> 3. Once the pg_basebackup completed, create appropriate recovery.conf on S1.

That was just recovery command and primary conninfo?

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services