Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 764866322CB for ; Wed, 7 Jan 2009 08:48:38 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 12047-05 for ; Wed, 7 Jan 2009 08:48:31 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.172]) by mail.postgresql.org (Postfix) with ESMTP id A613D6322C7 for ; Wed, 7 Jan 2009 08:48:30 -0400 (AST) Received: by wf-out-1314.google.com with SMTP id 25so8372173wfc.28 for ; Wed, 07 Jan 2009 04:48:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=2IKxcS1aK8ec0wdXLY6C/yc9fAyRczaCJlTb5qYInv0=; b=Efz8FuP12XMKJWMWyM1SHSq1M8XinbIV86hvTfcGR0EgO8wKxs9KPXEycxmK4U4goz jFazcu2kR1UgeOUlijhAqqhoTFJNpfz8H9xpV431gJEYFMV3mP4AdbgqAtKNKwORu71c 2/OcaTN8EIQ66kdzbFA3N56+iTY/zomFe/HXY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=ZxvOSYbIzUg6O8TUgNZgomJ0urZWfP29Ydjzl8b3UyEYFGGooSCjHZ0r0v6LAY4j1S vuoAGon4oozsgrq0HgXeGMD6sCLZXe5WEDesVEbVob5fvbym9DtMpJGd0kdyxzFihjsH M3IR9MmH830svrvtCcENYbFIs91DgT63ayDzc= Received: by 10.142.73.13 with SMTP id v13mr9636928wfa.195.1231332506194; Wed, 07 Jan 2009 04:48:26 -0800 (PST) Received: by 10.142.187.5 with HTTP; Wed, 7 Jan 2009 04:48:26 -0800 (PST) Message-ID: <965aa3ed0901070448i1f4e71as2e7cac9505c8ccfb@mail.gmail.com> Date: Wed, 7 Jan 2009 18:18:26 +0530 From: "Nimesh Satam" To: pgsql-performance@postgresql.org, "pgreplication-general@gborg.postgresql.org" , nsatam@zedo.com Subject: Sl_log_1 and sl_log_2 not getting truncated. MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_208435_22796920.1231332506180" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200901/25 X-Sequence-Number: 32304 ------=_Part_208435_22796920.1231332506180 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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. ------=_Part_208435_22796920.1231332506180 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi,

We have recently installed slony and tsrted replication on one o= f our test machines. When we start inserting data in to the replicated data= base, the replication is taking properly. Over a period of time the lag inc= reases between the two database.

Looking further we found that, sl_log_1 and sl_log2 are not getting tru= ncated. Following are the versions which we are using. Slony has been insta= lled 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_n= odelock entry for pid=3D17961
CONTEXT:  SQL statement "SELECT&= nbsp; "_inventorycluster".cleanupNodelock()"
PL/pgSQL function "cleanupevent" line 83 at PERFORM
NOTICE:&nb= sp; Slony-I: Logswitch to sl_log_1 initiated
CONTEXT:  SQL statemen= t "SELECT  "_inventorycluster".logswitch_start()"<= br>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  clea= nupThread: "vacuum  analyze "_inventorycluster".sl_even= t;" - 2009-01-06 22:10:43 PST ERROR  cleanupThread: "vacuum&= nbsp; analyze "_inventorycluster".sl_confirm;" - 2009-01-06 = 22:10:43 PST ERROR  cleanupThread: "vacuum  analyze "_i= nventorycluster".sl_setsync;" - 2009-01-06 22:10:43 PST ERROR&nbs= p; cleanupThread: "vacuum  analyze "_inventorycluster".= sl_log_1;" - 2009-01-06 22:10:43 PST ERROR  cleanupThread: "= vacuum  analyze "_inventorycluster".sl_log_2;" - 2009-0= 1-06 22:10:43 PST ERROR  cleanupThread: "vacuum  analyze &qu= ot;_inventorycluster".sl_seqlog;" - 2009-01-06 22:10:43 PST ERROR=   cleanupThread: "vacuum  analyze "_inventorycluster&qu= ot;.sl_archive_counter;" - 2009-01-06 22:10:43 PST ERROR  cleanup= Thread: "vacuum  analyze "pg_catalog".pg_listener;"= ; - 2009-01-06 22:10:43 PST ERROR  cleanupThread: "vacuum  a= nalyze "pg_catalog".pg_statistic;" - 2009-01-06 22:10:43 PST= INFO   cleanupThread:    0.280 seconds for vacuum= ing
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   cleanupTh= read:    0.127 seconds for cleanupEvent()

Regards,
Nimesh.

------=_Part_208435_22796920.1231332506180--