X-Original-To: pgsql-performance@postgresql.org Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id B672A47637E for ; Fri, 21 Mar 2003 01:18:34 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.8/8.12.8) with ESMTP id h2L6IWub010491; Fri, 21 Mar 2003 01:18:33 -0500 (EST) To: Florian Weimer Cc: pgsql-performance@postgresql.org Subject: Re: postgresql meltdown on PlanetMath.org In-reply-to: <87fzphk5hd.fsf@Login.CERT.Uni-Stuttgart.DE> References: <20030316060125.GD19570@vt.edu> <3E741B93.1090203@joeconway.com> <20030316075206.GE19570@vt.edu> <20030317061011.GH23355@perrin.int.nxad.com> <33137.130.15.224.150.1047881939.squirrel@mailbox.samurai.com> <495.1047882860@sss.pgh.pa.us> <15804.1047955909@sss.pgh.pa.us> <87fzphk5hd.fsf@Login.CERT.Uni-Stuttgart.DE> Comments: In-reply-to Florian Weimer message dated "Fri, 21 Mar 2003 00:01:18 +0100" Date: Fri, 21 Mar 2003 01:18:32 -0500 Message-ID: <10490.1048227512@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200303/152 X-Sequence-Number: 1450 Florian Weimer writes: > Hmm, are there any guidelines for choosing these values? > We have a database with a table into which we insert about 4,000,000 > rows each day, and delete another 4,000,000 rows. The total row count > is around 40 million, I guess, and the rows are about 150 bytes long. If you are replacing 10% of the rows in the table every day, then it's a pretty good bet that every single page of the table contains free space. Accordingly, you'd better set max_fsm_pages large enough to have a FSM slot for every page of the table. (1 page = 8Kb normally) You could possibly get away with a smaller FSM if you do (non-FULL) vacuums more often than once a day. Some people find they can run background vacuums without hurting performance too much, some don't --- I suspect it depends on how much spare disk bandwidth you have. regards, tom lane