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 80FDBD1B4E1 for ; Wed, 17 Sep 2003 20:22:22 +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 95138-03 for ; Wed, 17 Sep 2003 17:21:52 -0300 (ADT) Received: from yertle.kcilink.com (yertle.kcilink.com [216.194.193.105]) by svr1.postgresql.org (Postfix) with ESMTP id F3538D1B4EF for ; Wed, 17 Sep 2003 17:21:49 -0300 (ADT) Received: by yertle.kcilink.com (Postfix, from userid 100) id 7F4B8217B3; Wed, 17 Sep 2003 16:21:46 -0400 (EDT) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16232.49754.420785.943263@yertle.int.kciLink.com> Date: Wed, 17 Sep 2003 16:21:46 -0400 To: Robert Treat Cc: pgsql-performance@postgresql.org Subject: Re: restore time: sort_mem vs. checkpoing_segments In-Reply-To: <1063829746.25694.91.camel@camel> References: <16230.4066.565194.387700@yertle.int.kciLink.com> <1063829746.25694.91.camel@camel> 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/250 X-Sequence-Number: 3616 >>>>> "RT" == Robert Treat writes: RT> hmm... i wonder what would happen if you pushed your sort_mem higher... RT> on some of our development boxes and upgrade scripts, i push the RT> sort_mem to 102400 and sometimes even higher depending on the box. this RT> really speeds up my restores quit a bit (and is generally safe as i make RT> sure there isn't any other activity going on at the time) Ok... just two more tests to run, no big deal ;-) RT> another thing i like to do is turn of fsync, as if the system crashes in RT> the middle of reload i'm pretty sure i'd be starting all over anyway... I'll test it and see what happens. I suspect not a big improvement on a hardware RAID card with 128Mb backed up cache, though. But never say never!