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 C286D536FD for ; Wed, 30 Mar 2005 01:49:36 +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 49548-10 for ; Wed, 30 Mar 2005 00:49:29 +0000 (GMT) Received: from mailgate3.nau.edu (mailgate3.nau.edu [134.114.96.145]) by svr1.postgresql.org (Postfix) with ESMTP id CDFB6536DD for ; Wed, 30 Mar 2005 01:49:28 +0100 (BST) Received: from CONVERSION-DAEMON.mailgate3.nau.edu by mailgate3.nau.edu (PMDF V6.2-X17 #30845) id <0IE5007013MIT6@mailgate3.nau.edu> for pgsql-performance@postgresql.org; Tue, 29 Mar 2005 17:49:31 -0700 (MST) Received: from k2.cet.nau.edu (net9-213.cet.nau.edu [134.114.9.213]) by mailgate3.nau.edu (PMDF V6.2-X17 #30845) with ESMTP id <0IE500DN23MH3V@mailgate3.nau.edu> for pgsql-performance@postgresql.org; Tue, 29 Mar 2005 17:49:29 -0700 (MST) Date: Tue, 29 Mar 2005 17:52:58 -0700 From: Karim Nassar Subject: VACUUM on duplicate DB gives FSM and total pages discrepancies To: pgsql-performance@postgresql.org Message-id: <1112143978.9077.29.camel@k2.cet.nau.edu> MIME-version: 1.0 X-Mailer: Evolution 2.0.2 Content-type: text/plain Content-transfer-encoding: 7BIT X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/646 X-Sequence-Number: 11351 I recently pg_dumpall'd my DB from a (used for testing) v20z install of postgresql 8.0.1, and restored it to my production (but not yet in service) v40z running the same version. The test DB has had multiple millions of rows created/dropped during testing. The results of VACUUM VERBOSE are giving me pause: * v40z (hardly used after restore): orfs=# vacuum full analyze verbose; INFO: free space map: 114 relations, 84 pages stored; 1824 total pages needed DETAIL: Allocated FSM size: 1000 relations + 300000 pages = 1864 kB shared memory. VACUUM * v20z (after having undergone extensive tweaking, deletes, and inserts): orfs=# vacuum full analyze verbose; INFO: free space map: 53 relations, 13502 pages stored; 9776 total pages needed DETAIL: Allocated FSM size: 1000 relations + 300000 pages = 1864 kB shared memory. VACUUM 1) Should I be concerned about the total pages needed? ISTM that using that many more pages can't help but degrade relative performance on my testing machine. 2) How is it that my FSM has different numbers of relations? 3) Are either of these affects normal for an oft-used (or not) DB? FWIW: v40z v20z maintenance_work_mem 262144 16384 shared_buffers 30000 1000 Thanks, -- Karim Nassar Department of Computer Science Box 15600, College of Engineering and Natural Sciences Northern Arizona University, Flagstaff, Arizona 86011 Office: (928) 523-5868 -=- Mobile: (928) 699-9221