X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id AF959D1B56B for ; Tue, 23 Sep 2003 14:28:28 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 99781-09 for ; Tue, 23 Sep 2003 11:28:00 -0300 (ADT) Received: from yertle.kcilink.com (yertle.kcilink.com [216.194.193.105]) by svr1.postgresql.org (Postfix) with ESMTP id 5B6ABD1B4EB for ; Tue, 23 Sep 2003 11:27:56 -0300 (ADT) Received: by yertle.kcilink.com (Postfix, from userid 100) id 80FB5217B2; Tue, 23 Sep 2003 10:27:55 -0400 (EDT) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16240.22635.390707.785148@yertle.int.kciLink.com> Date: Tue, 23 Sep 2003 10:27:55 -0400 To: Bruce Momjian Cc: pgsql-performance@postgresql.org Subject: Re: restore time: sort_mem vs. checkpoing_segments In-Reply-To: <200309231359.h8NDx1A01317@candle.pha.pa.us> References: <16230.4066.565194.387700@yertle.int.kciLink.com> <200309231359.h8NDx1A01317@candle.pha.pa.us> X-Mailer: VM 7.14 under 21.4 (patch 12) "Portable Code" XEmacs Lucid X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/294 X-Sequence-Number: 3660 >>>>> "BM" == Bruce Momjian writes: BM> restore, even if there is no value to it being large during normal BM> server operation. Should that be decumented? Yes, right alongside the recommendation to bump sort_mem, even though in my tests sort_mem made no significant difference in restore time going from 8m to 128m.