On Tue, Feb 06, 2007 at 08:47:38PM -0500, [EMAIL PROTECTED] wrote:
> this has the ability to *empty* the tables should be an improvement.
>
> I can suggest one thing to take a particular look at, namely what indices
> are on sl_log_1 and sl_log_2.
>
> There should, over time, become a set of partial indexes on these tables
> based on the node numbers that are the origins of replication sets. That
> should be a help (e.g. - better performance than in 1.1, which didn't do
> this).
Because the transactions were big ones, also, those indexes may have
bad stats associated with them. Again, stopping slony (which is also
running a long transaction about now) may allow you to get the
analyse you need in place. Hmm. Also, check for locks that haven't
been granted.
A
--
Andrew Sullivan | [EMAIL PROTECTED]
A certain description of men are for getting out of debt, yet are
against all taxes for raising money to pay it off.
--Alexander Hamilton
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general