Re: Wrong SYSID in WAL segment

From: "Latrous, Youssef" <YLatrous(at)BroadViewNet(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Wrong SYSID in WAL segment
Date: 2010-10-25 20:33:53
Message-ID: 4B393627EE3CE74A9F189B639F857D2E02182B80@BVNYMAIL.bvn.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thank you for the reply.

This is an embedded system and is isolated (only the master and slave
nodes are reachable within this setup). Is there any way either the
slave or the master node changes the pg_control content? The Master node
did not restart at all when this happened. Moreover, if the slave is
rebooted, the problem goes away.

Regards,

Youssef

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Monday, October 25, 2010 4:12 PM
To: Latrous, Youssef
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Wrong SYSID in WAL segment

"Latrous, Youssef" <YLatrous(at)BroadViewNet(dot)com> 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2010-10-25 23:18:49 Re: [GENERAL] Gripe: bytea_output default => data corruption
Previous Message Tom Lane 2010-10-25 20:11:43 Re: Wrong SYSID in WAL segment