From: Vivek Khera <khera@kcilink.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: restore time: sort_mem vs. checkpoing_segments
Date: Tue, 16 Sep 2003 09:59:14 -0400
Message-ID: <16231.5938.817522.359405@yertle.int.kciLink.com> (raw)
In-Reply-To: <14070.1063689540@sss.pgh.pa.us>
References: <16230.4066.565194.387700@yertle.int.kciLink.com>
<14070.1063689540@sss.pgh.pa.us>
>>>>> "TL" == Tom Lane <tgl@sss.pgh.pa.us> writes:
TL> I was just bugging Marc for some useful data, so I'll ask you too:
TL> could you provide a trace of the pg_restore execution? log_statement
TL> plus log_duration output would do it. I am curious to understand
TL> exactly which steps in the restore are significant time sinks.
Sure... machine isn't gonna do much of anything until 7.4 is released
(or I hear a promise of no more dump/reload).
>> I notice during the restore that the disk throughput triples during
>> the checkpoint.
TL> Hm, better make sure the log includes some indication of when
TL> checkpoints happen.
That it does.
I'll post the results in the next couple of days, as each run takes
about 4 hours ;-)
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: khera@kcilink.com, tgl@sss.pgh.pa.us
Subject: Re: restore time: sort_mem vs. checkpoing_segments
In-Reply-To: <16231.5938.817522.359405@yertle.int.kciLink.com>
References: <16230.4066.565194.387700@yertle.int.kciLink.com> <14070.1063689540@sss.pgh.pa.us> <16231.5938.817522.359405@yertle.int.kciLink.com>
* 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