Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id DF8E19FB3E9 for ; Wed, 25 Oct 2006 19:31:01 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 24794-09 for ; Wed, 25 Oct 2006 19:30:54 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id B85829FA5D3 for ; Wed, 25 Oct 2006 19:30:53 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k9PMUqWW005752; Wed, 25 Oct 2006 18:30:52 -0400 (EDT) To: Mike Goldner cc: pgsql-admin@postgresql.org Subject: Re: Vacuum Problems (locking) In-reply-to: <1161806057.2095.154.camel@localhost.localdomain> References: <1161806057.2095.154.camel@localhost.localdomain> Comments: In-reply-to Mike Goldner message dated "Wed, 25 Oct 2006 15:54:17 -0400" Date: Wed, 25 Oct 2006 18:30:51 -0400 Message-ID: <5751.1161815451@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.127 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200610/166 X-Sequence-Number: 23469 Mike Goldner writes: > First of all, my max_fsm_pages is obviously way off. However, every > time I increase my max_fsm_pages the next vacuum says that it requires > more. Will there every be a plateau in the requested pages? We realized recently that this can happen if you have a single relation that all by itself needs more FSM space than you've got; any per-table space beyond max_fsm_pages is disregarded in the calculation of the total system-wide space needed, and so you get this inflationary effect where the reported requirement keeps going up when you increase the setting. There's a fix in for 8.2. > So, all indications point to postgres blocking all access during the > entire vacuum. You haven't said anything I consider credible evidence of that. But try looking in pg_locks next time. regards, tom lane