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 4C724D1B49E for ; Thu, 4 Dec 2003 18:36:36 +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 88923-07 for ; Thu, 4 Dec 2003 14:36:05 -0400 (AST) Received: from sardegna.mbigroup.it (unknown [151.8.40.3]) by svr1.postgresql.org (Postfix) with ESMTP id 3BFEFD1B444 for ; Thu, 4 Dec 2003 14:36:03 -0400 (AST) Received: from sicilia.pisa.mbigroup.it (localhost [127.0.0.1]) by sardegna.mbigroup.it (8.11.6/8.8.7) with ESMTP id hB4IZxe02358; Thu, 4 Dec 2003 19:35:59 +0100 Received: from bigfoot.com (canarie.pisa.mbigroup.it [192.168.9.30]) by sicilia.pisa.mbigroup.it (8.11.6/8.11.6) with ESMTP id hB4IZs301619; Thu, 4 Dec 2003 19:35:54 +0100 Message-ID: <3FCF7E74.9060604@bigfoot.com> Date: Thu, 04 Dec 2003 19:35:32 +0100 From: Gaetano Mendola User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031202 Thunderbird/0.4RC1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "pgsql-performance@postgresql.org" Cc: Vivek Khera 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> In-Reply-To: <16335.25079.106697.7521@yertle.int.kciLink.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/83 X-Sequence-Number: 4943 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); Regards Gaetano Mendola