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 8D48A474E53 for ; Mon, 17 Mar 2003 01:34:27 -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 h2H6YLub000496; Mon, 17 Mar 2003 01:34:21 -0500 (EST) To: "Neil Conway" Cc: sean@chittenden.org, logan@datacurrent.com, pgsql-performance@postgresql.org Subject: Re: postgresql meltdown on PlanetMath.org In-reply-to: <33137.130.15.224.150.1047881939.squirrel@mailbox.samurai.com> 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> Comments: In-reply-to "Neil Conway" message dated "Mon, 17 Mar 2003 01:18:59 -0500" Date: Mon, 17 Mar 2003 01:34:20 -0500 Message-ID: <495.1047882860@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200303/115 X-Sequence-Number: 1413 "Neil Conway" writes: > Sean Chittenden said: > A "select count(*) FROM tblwordidx" initially took about 1 second to > return a count of 2 million but after a few months it took several > minutes of really hard HDD grinding. >> >> That's because there are dead entries in the index that weren't being >> reused or cleaned up. As I said, this has been fixed. > That's doubtful: "select count(*) FROM foo" won't use an index. To know what's going on, as opposed to guessing about it, we'd need to know something about the physical sizes of the table and its indexes. "vacuum verbose" output would be instructive... But my best theorizing-in-advance-of-the-data guess is that Logan's FSM settings are too small, causing free space to be leaked over time. If a vacuum full restores the original performance then that's probably the right answer. regards, tom lane