X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id ADA72D1C9DA for ; Fri, 16 Apr 2004 16:10:40 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 45973-05 for ; Fri, 16 Apr 2004 16:10:29 -0300 (ADT) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 966EED1C9BE for ; Fri, 16 Apr 2004 16:10:31 -0300 (ADT) Received: from [64.81.245.111] (HELO 192.168.1.102) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 4876284; Fri, 16 Apr 2004 12:11:55 -0700 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Ron St-Pierre , pgsql-performance@postgresql.org Subject: Re: Index Problem? Date: Fri, 16 Apr 2004 12:10:47 -0700 User-Agent: KMail/1.5.4 References: <40800CC2.3050707@syscor.com> <200404161001.52989.josh@agliodbs.com> <40801E1B.4020401@syscor.com> In-Reply-To: <40801E1B.4020401@syscor.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200404161210.47995.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/223 X-Sequence-Number: 6523 Ron, > Yeah I agree but I'm not allowed to remove those indexes. It's not the indexes I'm talking about, it's the table. > On my dev server I increased max_fsm_pages from the default of 20000 to > 40000, A better way to set this would be to run VACUUM VERBOSE ANALYZE right after doing one of your update batches, and see how many dead pages are being reclaimed, and then set max_fsm_pages to that # + 50% (or more). increased checkpoint_segments from 3 to 5, and the function ran > in about 6-7 minutes which is a nice increase. According to the docs > "Annotated postgresql.conf and Global User Configuration (GUC) Guide" on > varlena I'll have to re-start postgres for the changes to take effect > there (correct?). Correct. > Also the docs on Varlena show the max_fsm_pages > default to be 10,000 but my default was 20,000, looks like that needs > updating. I don't think the default has been changed. Anyone? -- -Josh Berkus Aglio Database Solutions San Francisco