Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 840389FC195 for ; Fri, 25 May 2007 10:57:27 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 54173-08 for ; Fri, 25 May 2007 10:57:21 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id B94E09FC18B for ; Fri, 25 May 2007 10:57:21 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l4PDvK6F008328; Fri, 25 May 2007 09:57:20 -0400 (EDT) To: Nicola Mauri cc: pgsql-admin@postgresql.org Subject: Re: Abnormal storage consumption with autovacuum enabled In-reply-to: <46569EF1.1080106@saga.it> References: <46569EF1.1080106@saga.it> Comments: In-reply-to Nicola Mauri message dated "Fri, 25 May 2007 10:31:45 +0200" Date: Fri, 25 May 2007 09:57:19 -0400 Message-ID: <8327.1180101439@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/282 X-Sequence-Number: 25602 Nicola Mauri writes: >> What do you have max_fsm_pages set to? > Currently, max_fsm_pages=20000 > Running VACUUM VERBOSE reports: > NOTICE: number of page slots needed (237312) exceeds max_fsm_pages (20000) > HINT: Consider increasing the configuration parameter "max_fsm_pages" to a value over 237312. Yup, there's your problem (or a huge chunk of it anyway). > Is this measurement reliable? > We are considering to set: max_fsm_pages=400000 > Could this have some sort of impact? It will require a slightly larger shared-memory segment than you have now. regards, tom lane