On Jun 12, 2007, at 6:24 AM, James Tucker wrote:
I've recently configured slony to replicate our production databases. One of the databases has ceased replicating and I can see events queueing in sl_status. On the subscriber node I have one connection "idle in transaction" to postgresql running as the slony user. I see no errors, warnings or even notices in the logs, just debug level sync events which appear to be going through ok.
but *how* long is that transaction idle? ie, is it idle for hours or just a few seconds at a time. usually when you see this it is because the origin is taking a long time sending the rows to the client to apply for the sync set.
try cranking up the slony logging to level 4 and see how long it takes to fetch each set of rows for the updates. You could have had one big transaction on the origin that is just taking a long time to apply.
_______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
