From: | "Nimesh Satam" <nimesh(dot)zedo(at)gmail(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org, "pgreplication-general(at)gborg(dot)postgresql(dot)org" <pgreplication-general(at)gborg(dot)postgresql(dot)org>, nsatam(at)zedo(dot)com |
Subject: | Sl_log_1 and sl_log_2 not getting truncated. |
Date: | 2009-01-07 12:48:26 |
Message-ID: | 965aa3ed0901070448i1f4e71as2e7cac9505c8ccfb@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi,
We have recently installed slony and tsrted replication on one of our test
machines. When we start inserting data in to the replicated database, the
replication is taking properly. Over a period of time the lag increases
between the two database.
Looking further we found that, sl_log_1 and sl_log2 are not getting
truncated. Following are the versions which we are using. Slony has been
installed for the first time
Postgres version: 8.3.5
slony version: 2.0.0
Can someone let me know what we should be looking at?
Following is the error which we get:
NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=17961
CONTEXT: SQL statement "SELECT "_inventorycluster".cleanupNodelock()"
PL/pgSQL function "cleanupevent" line 83 at PERFORM
NOTICE: Slony-I: Logswitch to sl_log_1 initiated
CONTEXT: SQL statement "SELECT "_inventorycluster".logswitch_start()"
PL/pgSQL function "cleanupevent" line 101 at PERFORM
2009-01-06 22:10:43 PST INFO cleanupThread: 0.149 seconds for
cleanupEvent()
2009-01-06 22:10:43 PST ERROR cleanupThread: "vacuum analyze
"_inventorycluster".sl_event;" - 2009-01-06 22:10:43 PST ERROR
cleanupThread: "vacuum analyze "_inventorycluster".sl_confirm;" -
2009-01-06 22:10:43 PST ERROR cleanupThread: "vacuum analyze
"_inventorycluster".sl_setsync;" - 2009-01-06 22:10:43 PST ERROR
cleanupThread: "vacuum analyze "_inventorycluster".sl_log_1;" - 2009-01-06
22:10:43 PST ERROR cleanupThread: "vacuum analyze
"_inventorycluster".sl_log_2;" - 2009-01-06 22:10:43 PST ERROR
cleanupThread: "vacuum analyze "_inventorycluster".sl_seqlog;" - 2009-01-06
22:10:43 PST ERROR cleanupThread: "vacuum analyze
"_inventorycluster".sl_archive_counter;" - 2009-01-06 22:10:43 PST ERROR
cleanupThread: "vacuum analyze "pg_catalog".pg_listener;" - 2009-01-06
22:10:43 PST ERROR cleanupThread: "vacuum analyze
"pg_catalog".pg_statistic;" - 2009-01-06 22:10:43 PST INFO
cleanupThread: 0.280 seconds for vacuuming
NOTICE: Slony-I: log switch to sl_log_1 still in progress - sl_log_2 not
truncated
CONTEXT: PL/pgSQL function "cleanupevent" line 99 at assignment
2009-01-06 22:21:31 PST INFO cleanupThread: 0.127 seconds for
cleanupEvent()
Regards,
Nimesh.
From | Date | Subject | |
---|---|---|---|
Next Message | jose fuenmayor | 2009-01-07 13:58:17 | Fwd: Casting issue!! |
Previous Message | Simon Waters | 2009-01-07 09:31:25 | Re: understanding postgres issues/bottlenecks |