X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 43765D1B436 for ; Mon, 8 Dec 2003 00:47:28 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 17543-09 for ; Sun, 7 Dec 2003 20:47:00 -0400 (AST) Received: from pns.mm.eutelsat.org (pns.mm.eutelsat.org [194.214.173.227]) by svr1.postgresql.org (Postfix) with ESMTP id 78E3DD1B46F for ; Sun, 7 Dec 2003 20:46:56 -0400 (AST) Received: from nts-03.mm.eutelsat.org (localhost [127.0.0.1]) by pns.mm.eutelsat.org (8.11.6/linuxconf) with ESMTP id hB80oCs01675 for ; Mon, 8 Dec 2003 01:50:12 +0100 Received: from bigfoot.com (accesspoint.mm.eutelsat.org [194.214.173.4]) by nts-03.mm.eutelsat.org (8.11.6/linuxconf) with ESMTP id hB80ZRR16821 for ; Mon, 8 Dec 2003 01:35:27 +0100 Message-ID: <3FD3C9DA.5040805@bigfoot.com> Date: Mon, 08 Dec 2003 01:46:18 +0100 From: Gaetano Mendola User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031206 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "pgsql-performance@postgresql.org" Subject: Re: autovacuum daemon stops doing work after about an hour References: <16332.63508.196365.801418@yertle.int.kciLink.com> <1070516326.1455.11.camel@zedora.zeut.net> <16335.25079.106697.7521@yertle.int.kciLink.com> <3FCF7E74.9060604@bigfoot.com> In-Reply-To: <3FCF7E74.9060604@bigfoot.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/149 X-Sequence-Number: 5009 Gaetano Mendola wrote: > Vivek Khera wrote: > >>>>>>> "MTO" == Matthew T O'Connor writes: >> >> >> >>>> Then it just sits there. I started it at 11:35am, and it is now >>>> 3:30pm. >> >> >> >> MTO> Weird.... Alphabetically speaking, is vkmlm."public"."user_list" >> be the >> MTO> last table in the last schema in the last database? You are running >> >> conveniently, yes it is... >> >> MTO> with -d4, so you would get a message about going to sleep shortly >> after >> MTO> dealing with the last table, but you didn't get the sleep >> message, so I >> MTO> don't think the problem is that pg_autovacuum is sleeping for an >> MTO> inordinate amount time. >> >> The only sleep logged was >> >> [2003-12-03 04:47:13 PM] 1 All DBs checked in: 84996853 usec, will >> sleep for 469 secs. > > > What I seen is: > > > # tail -f auto.log > [2003-12-04 07:10:18 PM] reltuples: 72; relpages: 1 > [2003-12-04 07:10:18 PM] curr_analyze_count: 72; cur_delete_count: 0 > [2003-12-04 07:10:18 PM] ins_at_last_analyze: 72; del_at_last_vacuum: 0 > [2003-12-04 07:10:18 PM] insert_threshold: 572; delete_threshold 536 > [2003-12-04 07:10:18 PM] table name: empdb."public"."contracts" > [2003-12-04 07:10:18 PM] relfilenode: 17784; relisshared: 0 > [2003-12-04 07:10:18 PM] reltuples: 347; relpages: 5 > [2003-12-04 07:10:18 PM] curr_analyze_count: 347; cur_delete_count: 0 > [2003-12-04 07:10:18 PM] ins_at_last_analyze: 347; del_at_last_vacuum: 0 > [2003-12-04 07:10:18 PM] insert_threshold: 847; delete_threshold 673 > > > [ 5 minutes of delay ] <----- LOOK THIS > > > [2003-12-04 07:10:18 PM] 503 All DBs checked in: 179396 usec, will sleep > for 300 secs. > [2003-12-04 07:15:19 PM] 504 All DBs checked in: 98814 usec, will sleep > for 300 secs. > > I think is a good Idea put a fflush after: > > fprintf(LOGOUTPUT, "[%s] %s\n", timebuffer, logentry); Was I wrong ? If you are watching in tail the log believeme is really annoying. Regards Gaetano Mendola