Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TpH6e-0006fH-P6 for pgsql-admin@arkaria.postgresql.org; Sun, 30 Dec 2012 11:31:04 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1TpH6d-0007mn-NR for pgsql-admin@arkaria.postgresql.org; Sun, 30 Dec 2012 11:31:03 +0000 Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TpH6b-0007md-Ff for pgsql-admin@postgresql.org; Sun, 30 Dec 2012 11:31:01 +0000 Received: from nm24-vm1.bullet.mail.ne1.yahoo.com ([98.138.90.45]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TpH6W-0003ZW-3Y for pgsql-admin@postgresql.org; Sun, 30 Dec 2012 11:31:00 +0000 Received: from [98.138.226.178] by nm24.bullet.mail.ne1.yahoo.com with NNFMP; 30 Dec 2012 11:30:55 -0000 Received: from [98.138.89.162] by tm13.bullet.mail.ne1.yahoo.com with NNFMP; 30 Dec 2012 11:30:55 -0000 Received: from [127.0.0.1] by omp1018.mail.ne1.yahoo.com with NNFMP; 30 Dec 2012 11:30:55 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 132998.82465.bm@omp1018.mail.ne1.yahoo.com Received: (qmail 25361 invoked by uid 60001); 30 Dec 2012 11:30:55 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1356867055; bh=Ak6Zn4ebHNa7+vSfGS2Kdt3+6AjGHXldf6uIngVtcsI=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=NvK+wrnsYJLYmYwD0MntQAaG9iOuV1/V+0f2Z4E8sKmOmyzv+xBeIM698lgxCQwmO3RJVxInMvl9yKlvJ1JScaISDcNuNpqkBXMrmKm0aH7B26sTq4hI499lXd5NzQXErF/rNIg+NEGgzjLgouPDS1DWXI4ysHA38sc6qMbQNVE= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=1+irfEEchQNeRxrXwoRFdfFsHV79gMkgDybWu3j5Yu3A8Zt1dT53Ktfy/30Ptfib0AaWjM+hVmEFe4QTyvCozQ91tCU3/N2H2Fss6Y17r/QWfnnBzIJ1EaN3UNGVZOEXBXGivRkF4Ket4/dxfYLtQqwcErRHgVuH79O/ONqFjzM=; X-YMail-OSG: wSntyFIVM1llISOZWku3o_ZqZvXM7yIcd1eHnkbpm5Z.Hn_ 9Kwez76U9HQEXKXhsjZh3wzEfSpaX_9Yq6sb3IacqB.XyOx51tGQANlb3ENi FCRnQHJC2Phe.X59v1i62LnX28tGu1rlzMASDsIRNDWsL9NnqxUARtQ095JI DQr7P_CaAGC36GWkAGKrzTwtA8ydqtAda2YG_Jt9zmr73LkPDEqVc36rZua_ ZIiOsT3WUBgo66nSx2YdqCzAXdueu5ZWErpWBB9odSx61y3IOjwHtY7pw4S2 AUBOb8UU2a4KqX5YkSCjgXemI1RRMltseIq7LLvxgo6sRtWc6teQJhclUy2O 6snask9r1VsAFmzBYnOT366bDZQ0XJGubX9DCgw8MwztOgLTz6iML70l2SHR .CnMtTocWwNLeFOMA4.5xsX.78XWX2X52TmljeuNTrbOf4VNOkMA4l3jpLx5 NNmecwkGCQmZna4a.Wc.lIOkk55.igEcLrxUm6Kih8zIU.OH3YmNL03BWJos - Received: from [98.210.146.78] by web125903.mail.ne1.yahoo.com via HTTP; Sun, 30 Dec 2012 03:30:54 PST X-Rocket-MIMEInfo: 001.001, CgpTdWhhcyAtLQoKCj4KPkNhbiBpIGNhbmNlbMKgIG9uZ29pbmcgYXV0b3ZhY3V1bSBvbiBhIGxhcmdlIHRhYmxlPyBJcyBpdCBzYWZlPwo.Cj5JIGFtIHRyeWluZyB0byBkbyBwZ19jYW5jZWxfYmFja2VuZChwcm9jaWQpLlBsZWFzZSBzdWdnZXN0IHdoZXRoZXIgaXRzIHNhZmUKPnRvIGRvID8KPgo.UmdyZHMKPlN1aGFzCj4KPgpJJ3ZlIGtpbGxlZCBhdXRvdmFjIHByb2Nlc3NlcyBtYW51YWxseSB3aXRoIG5vIG1hbGlnbiBlZmZlY3RzIG90aGVyIHRoYW4gdGhlIGNvbnNlcXVlbmNlcyBvZiBub3QgdmFjdXUBMAEBAQE- X-Mailer: YahooMailWebService/0.8.129.483 References: <1356863452778-5738332.post@n5.nabble.com> Message-ID: <1356867054.25225.YahooMailNeo@web125903.mail.ne1.yahoo.com> Date: Sun, 30 Dec 2012 03:30:54 -0800 (PST) From: Greg Williamson Reply-To: Greg Williamson Subject: Re: autovacuum To: "pgsql-admin@postgresql.org" In-Reply-To: <1356863452778-5738332.post@n5.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Pg-Spam-Score: 1.3 (+) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Suhas -- > >Can i cancel=A0 ongoing autovacuum on a large table? Is it safe? > >I am trying to do pg_cancel_backend(procid).Please suggest whether its safe >to do ? > >Rgrds >Suhas > > I've killed autovac processes manually with no malign effects other than th= e consequences of not vacuuming the table involved. This may depend some on what version of postgres -- that may make a differe= nce. My experience is with 8.4 and 9.1 and both have been OK (although on o= ne database the autovac is set to be very aggressive so it starts again alm= ost immediately. You may need to tweak the config settings if that is the c= ase). But I have usually found that autovac solves far more problems than it caus= es. You may want to post more details about version and config settings related= to autovac that differ from defaults. That might help get a better answer,= and might help with whatever problem you think autovac is causing. HTH, Greg Williamson --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin