X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 3DE323A1D9E for ; Fri, 29 Oct 2004 15:37:29 +0100 (BST) 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 48787-09 for ; Fri, 29 Oct 2004 14:37:21 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 25CD43A1D9C for ; Fri, 29 Oct 2004 15:37:24 +0100 (BST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id i9TEbOql015930; Fri, 29 Oct 2004 10:37:24 -0400 (EDT) To: Patrick Hatcher Cc: pgsql-performance@postgresql.org Subject: Re: determining max_fsm_pages In-reply-to: <41824E05.8000903@comcast.net> References: <41824E05.8000903@comcast.net> Comments: In-reply-to Patrick Hatcher message dated "Fri, 29 Oct 2004 07:04:53 -0700" Date: Fri, 29 Oct 2004 10:37:23 -0400 Message-ID: <15929.1099060643@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/470 X-Sequence-Number: 8946 Patrick Hatcher writes: > My question is this: I have about 8 databases running on this server. > When I do a vacuum full on each of these databases, there is a INFO > section that I assume is the total pages used for that database. Should > add ALL these individual pages together and pad the total and use this > as my new max_fsm_pages? Should I do the same thing with max_fsm_relations? No, the numbers shown at the end of a vacuum verbose printout reflect the current cluster-wide FSM demand. BTW you do *not* want to use FULL because that's not going to reflect the FSM requirements when you are just running normal vacuums. I would vacuum all your databases (to make sure each one's FSM contents are pretty up-to-date) and then take the numbers shown by the last one as your targets. If you find yourself having to raise max_fsm_relations, it may be necessary to repeat the vacuuming cycle before you can get a decent total for max_fsm_pages. IIRC, the vacuum printout does include in "needed" a count of pages that it would have stored if it'd had room; but this is only tracked for relations that have an FSM relation entry. regards, tom lane