pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedSl_log_1 and sl_log_2 not getting truncated.
2+ messages / 2 participants
[nested] [flat]
* Sl_log_1 and sl_log_2 not getting truncated.
@ 2009-01-07 12:48 Nimesh Satam <nimesh.zedo@gmail.com>
0 siblings, 1 reply; 2+ messages in thread
From: Nimesh Satam @ 2009-01-07 12:48 UTC (permalink / raw)
To: pgsql-performance@postgresql.org, "pgreplication-general@gborg.postgresql.org" <pgreplication-general@gborg.postgresql.org>; nsatam@zedo.com
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.
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Sl_log_1 and sl_log_2 not getting truncated.
@ 2009-01-07 15:41 Brad Nicholson <bnichols@ca.afilias.info>
parent: Nimesh Satam <nimesh.zedo@gmail.com>
0 siblings, 0 replies; 2+ messages in thread
From: Brad Nicholson @ 2009-01-07 15:41 UTC (permalink / raw)
To: Nimesh Satam <nimesh.zedo@gmail.com>; +Cc: pgsql-performance@postgresql.org, "pgreplication-general@gborg.postgresql.org" <pgreplication-general@gborg.postgresql.org>; nsatam@zedo.com
On Wed, 2009-01-07 at 18:18 +0530, Nimesh Satam wrote:
> 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.
You should sign up to the Slony list and ask your question there.
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2009-01-07 15:41 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2009-01-07 12:48 Sl_log_1 and sl_log_2 not getting truncated. Nimesh Satam <nimesh.zedo@gmail.com>
2009-01-07 15:41 ` Brad Nicholson <bnichols@ca.afilias.info>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox