cbbrowne wrote:
> Geoffrey wrote:
>> Noticed yesterday that the same two tables on all our databases (12) 
>> are out of sync.  I've just noticed today that the date on the slave 
>> is 1 hour behind the master.  Is it possible that this time difference 
>> could cause any problems with slony replication?
>>
> In what sense are they "out of sync"?

The slave is way behind record count wise.  Lag is not an issue.  For 
example, one table the count of records on the master node is 1500, on 
the slave it is 762.

> Slony-I doesn't use timestamps to control its behaviour; it uses 
> internal transaction IDs, so this seems rather surprising.
> 
> I'd appreciate it a lot if you could do some poking at it to see if you 
> could determine where specifically the problem arose, as  it would be a 
> LOT better to be able to give specific diagnosis of "make sure X doesn't 
> happen to your system!" rather than merely saying "oh, you shouldn't let 
> times get TOO out of sync otherwise there might be some problems..."

I suspect that this was caused by the truncation of these tables on the 
master node.  See the other recent threads around this issue.

Looking in the logs, I don't really see anything that would tell me 
there was a problem.

Basically, there is a year end process that truncates two tables on all 
our databases.  I was unaware that slony would not replicate the 
truncation process.

The thing that confuses me about this is that I would have expected the 
slave node to have a higher record count then the master, since the 
master was truncated.

-- 
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
  - Benjamin Franklin