X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 85543D801A for ; Sun, 28 Aug 2005 15:49:02 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 55050-03 for ; Sun, 28 Aug 2005 18:49:00 +0000 (GMT) Received: from 217-20-115-93.internetserviceteam.com (217-20-115-93.internetserviceteam.com [217.20.115.93]) by svr1.postgresql.org (Postfix) with ESMTP id 1E0B1D8006 for ; Sun, 28 Aug 2005 15:48:59 -0300 (ADT) Received: from [192.168.1.122] (146.Red-83-38-136.pooles.rima-tde.net [83.38.136.146]) by 217-20-115-93.internetserviceteam.com (Postfix) with ESMTP id 55DC3395E1; Sun, 28 Aug 2005 20:00:16 +0200 (CEST) Message-ID: <43120713.7000003@mediaroot.de> Date: Sun, 28 Aug 2005 19:48:51 +0100 From: Aldor User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: pgsql-admin@postgresql.org Subject: Re: VACUUM - How long should it take?! - Here are some test References: <4311DFD5.6000104@mediaroot.de> <25202.1125247612@sss.pgh.pa.us> In-Reply-To: <25202.1125247612@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.857 required=5 tests=[PLING_QUERY=0.857] X-Spam-Level: X-Archive-Number: 200508/367 X-Sequence-Number: 18686 >>bgwriter_percent = 0 >>bgwriter_maxpages = 0 > Why did you do that? There's certainly nothing in the docs recommending > disabling the bgwriter. I'm remembering that putting big data into the database ran faster with this settings. >>The duration of the VACUUM of tbl1 and tbl2 is okay - so how to speed up >>now the VACUUM of tbl3? > > > You have not showed us anything that would explain any speed differences > between these tables. Maybe there was some difference in the data you > loaded them with? The strings in the tbl3 are longer - I took the average length from the original table which is about 94 characters. I will make some tests with increasing the data in tbl3 with 100k, 1 Million and 100 Million rows. I'll also try activating the bgwriter. The other settings in postgresql.conf look for you ok? Some other information ---------------------- Distribution: Debian Encoding of Database: LATIN10 Locale: C Regards, Aldor Tom Lane wrote: > Aldor writes: > >>bgwriter_percent = 0 >>bgwriter_maxpages = 0 > > > Why did you do that? There's certainly nothing in the docs recommending > disabling the bgwriter. > > >>The duration of the VACUUM of tbl1 and tbl2 is okay - so how to speed up >>now the VACUUM of tbl3? > > > You have not showed us anything that would explain any speed differences > between these tables. Maybe there was some difference in the data you > loaded them with? > > regards, tom lane >