From: Tom Lane <tgl@sss.pgh.pa.us>
To: Vivek Khera <khera@kcilink.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: restore time: sort_mem vs. checkpoing_segments
Date: Tue, 16 Sep 2003 01:19:00 -0400
Message-ID: <14070.1063689540@sss.pgh.pa.us> (raw)
In-Reply-To: <16230.4066.565194.387700@yertle.int.kciLink.com>
References: <16230.4066.565194.387700@yertle.int.kciLink.com>
Vivek Khera <khera@kcilink.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, khera@kcilink.com
Subject: Re: restore time: sort_mem vs. checkpoing_segments
In-Reply-To: <14070.1063689540@sss.pgh.pa.us>
References: <16230.4066.565194.387700@yertle.int.kciLink.com> <14070.1063689540@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox