I get the same "weird" errors (WAL file is from different database system)
too with Ubuntu and Postgresql 9.3 when setting up a slave using rsync.
1. I installed postgresql on the slave (which automatically does the
initdb):
sudo apt-get install postgresql-9.3
2. Modified my postgresql.conf fi
On Fri, Aug 9, 2013 at 9:54 AM, Quentin Hartman
wrote:
> OK, figured this out. I had it start copying the pg_xlog directory as well
> when doing the initial sync. I realized this is also the first time I've
> setup replication from scratch using 9.2. All my other 9.2 pairs were setup
> on either 9
On Fri, Aug 9, 2013 at 8:33 AM, Quentin Hartman
wrote:
> This pair of servers aren't replacing anything, they are new, empty servers.
That should be 'empty server', singular.
> Before starting the slave at all, I'm copying the entire data filestructure
> over to it via rsync. I'm doing almost ex
OK, figured this out. I had it start copying the pg_xlog directory as well
when doing the initial sync. I realized this is also the first time I've
setup replication from scratch using 9.2. All my other 9.2 pairs were setup
on either 9.0 or 9.1, and have been upgraded from there with replication
al
This pair of servers aren't replacing anything, they are new, empty
servers. Before starting the slave at all, I'm copying the entire data
filestructure over to it via rsync. I'm doing almost exactly what is
described here:
http://wiki.postgresql.org/wiki/Binary_Replication_Tutorial#Binary_Replicat
On Fri, Aug 9, 2013 at 8:55 AM, Quentin Hartman
wrote:
> 2013-08-08 23:47:30 GMT LOG: WAL file is from different database system
> 2013-08-08 23:47:30 GMT DETAIL: WAL file database system identifier is
> 5909892614333033983, pg_control database system identifier is
> 5909892824786287231.
It look
