On Tue, Feb 06, 2007 at 02:37:12PM -0600, Dan Falconer wrote:
> I'm not trying to blame-shift here, but it really seems like
> the lag is generated from Slony itself. There's a stale
> connection, initiated by Slony (that's the only thing that connects
> on the private 192.168.1.x network), which sits idle in
> transaction. On the master, the query shows as "fetch 100 from
> LOG;" and shows on the slave as "<IDLE> in transaction".
I think you're suffering from the log bloat problem. I'd try
stopping slony, performing vacuum analyse on that table, and then
starting again. But my real guess is that this approach is not going
to work very well for you. :(
A
--
Andrew Sullivan | [EMAIL PROTECTED]
Unfortunately reformatting the Internet is a little more painful
than reformatting your hard drive when it gets out of whack.
--Scott Morris
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
