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 B4B8CD1B4E2 for ; Tue, 16 Sep 2003 05:19:12 +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 29345-01 for ; Tue, 16 Sep 2003 02:19:03 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id BA5FDD1B4F1 for ; Tue, 16 Sep 2003 02:19:01 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h8G5J04A014071; Tue, 16 Sep 2003 01:19:00 -0400 (EDT) To: Vivek Khera Cc: pgsql-performance@postgresql.org Subject: Re: restore time: sort_mem vs. checkpoing_segments In-reply-to: <16230.4066.565194.387700@yertle.int.kciLink.com> References: <16230.4066.565194.387700@yertle.int.kciLink.com> Comments: In-reply-to Vivek Khera message dated "Mon, 15 Sep 2003 15:15:46 -0400" Date: Tue, 16 Sep 2003 01:19:00 -0400 Message-ID: <14070.1063689540@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/231 X-Sequence-Number: 3597 Vivek Khera writes: > Restore of a significanly big database (~19.8GB restored) shows nearly > no time difference depending on sort_mem when checkpoint_segments is > large. There are quite a number of tables and indexes. The restore > was done from a pg_dump -Fc dump of one database. I was just bugging Marc for some useful data, so I'll ask you too: could you provide a trace of the pg_restore execution? log_statement plus log_duration output would do it. I am curious to understand exactly which steps in the restore are significant time sinks. > I notice during the restore that the disk throughput triples during > the checkpoint. Hm, better make sure the log includes some indication of when checkpoints happen. regards, tom lane