Hi there,
In one of our systems we've noticed the following (strange?) behavior.
In a Master/Slave configuration, we run wal-mgr to achieve data
replication from the master to the slave node. Both nodes run PostgreSQL
8.4.1 (on Solaris 10). The slave starts in archive mode and initiates a
resto
"Latrous, Youssef" writes:
> 1) Why one of the segments has a different SYSID (knowing that all WAL
> segments are originating from the same node)?
They aren't. Somewhere you've got WAL segments slipping in from a
different database cluster.
regards, tom lane
--
Sent v
slave is
rebooted, the problem goes away.
Regards,
Youssef
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Monday, October 25, 2010 4:12 PM
To: Latrous, Youssef
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Wrong SYSID in WAL segment
"Latrous, Yo
