X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id F217E9F94EA for ; Wed, 24 May 2006 16:48:49 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 25089-08 for ; Wed, 24 May 2006 16:48:44 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 0E4D49F9398 for ; Wed, 24 May 2006 16:48:43 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k4OJmcik001127; Wed, 24 May 2006 15:48:39 -0400 (EDT) To: "Todd A. Cook" cc: Ruairi , pgsql-admin@postgresql.org Subject: Re: Restore of pg_dump taking a long time... In-reply-to: <4474B721.8040101@blackducksoftware.com> References: <008c01c67f26$9848caf0$2815a8c0@D5T7W62J> <468.1148496451@sss.pgh.pa.us> <4474B721.8040101@blackducksoftware.com> Comments: In-reply-to "Todd A. Cook" message dated "Wed, 24 May 2006 15:42:25 -0400" Date: Wed, 24 May 2006 15:48:38 -0400 Message-ID: <1126.1148500118@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/341 X-Sequence-Number: 21873 "Todd A. Cook" writes: > I have found that increasing maintenance_work_mem can decrease index > build speed on large tables: You should probably re-measure when 8.2 comes out; we've fixed a number of performance issues in the sorting code that might cause that. regards, tom lane