Try turning your log levels up higher so there's more hints about what's going on.
Also, you want to make sure you're not being clobbered by the statement_timeout stuff. On 4/3/07, Andrew Edson <[EMAIL PROTECTED]> wrote: > I am attempting to test replication across a pair of systems. I have > noticed that semi-large replication jobs seem to have trouble getting > replicated, whereas smaller jobs are replicated with no problems. As of > today, an update with ~190,000 items involved was prevented from > replicating. Looking at the output of the slon running on that system, I > discovered the following: > > > 2007-04-03 07:43:16 CDT CONFIG enableNode: no_id=1 > 2007-04-03 07:43:16 CDT DEBUG1 main: running scheduler mainloop > 2007-04-03 07:43:16 CDT DEBUG1 remoteListenThread_1: thread starts > 2007-04-03 07:43:16 CDT DEBUG1 cleanupThread: thread starts > 2007-04-03 07:43:16 CDT DEBUG1 syncThread: thread starts > 2007-04-03 07:43:16 CDT DEBUG1 remoteWorkerThread_1: thread starts > 2007-04-03 07:43:16 CDT DEBUG1 remoteWorkerThread_1: helper thread for > provider 1 created > 2007-04-03 07:43:17 CDT DEBUG1 remoteListenThread_1: connected to > 'dbname=test_attest host=10.10.10.176 user=postgres' > 2007-04-03 07:43:17 CDT DEBUG1 remoteWorkerThread_1: connected to data > provider 1 on 'dbname=test_attest host=10.10.10.176 user=postgres' > 2007-04-03 07:48:54 CDT DEBUG1 slon: shutdown requested > 2007-04-03 07:48:54 CDT DEBUG1 syncThread: thread done > 2007-04-03 07:48:54 CDT INFO remoteListenThread_1: disconnecting from > 'dbname=test_attest host=10.10.10.176 user=postgres' > 2007-04-03 07:48:54 CDT DEBUG1 remoteListenThread_1: thread done > 2007-04-03 07:48:54 CDT DEBUG1 localListenThread: thread done > 2007-04-03 07:48:54 CDT DEBUG1 cleanupThread: thread done > 2007-04-03 07:48:54 CDT DEBUG1 main: scheduler mainloop returned > 2007-04-03 07:49:14 CDT WARN main: shutdown timeout exiting > 2007-04-03 07:49:14 CDT DEBUG1 slon: shutdown now requested > > I'm new enough to slony replication that I have no clue what the problem is, > only that, for some reason, the subscriber node appears to have ditched the > connection to the provider node in my setup. What is a likely cause of > this, and where would I turn in the docs to figure out how to prevent it? > > ________________________________ > Looking for earth-friendly autos? > Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center. > > > _______________________________________________ > Slony1-general mailing list > [email protected] > http://gborg.postgresql.org/mailman/listinfo/slony1-general > > _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
