From: Gavin Sherry <swm@alcove.com.au>
To: Brendan Duddridge <brendan@clickspace.com>
Cc: Tomas Vondra <tv@fuzzy.cz>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: Recovery will take 10 hours
Date: Fri, 21 Apr 2006 11:15:28 +1000 (EST)
Message-ID: <Pine.LNX.4.58.0604211112400.17115@linuxworld.com.au> (raw)
In-Reply-To: <5C372D71-D189-4AA7-A857-1C8FE42311AE@clickspace.com>
References: <85A15B2E-F59C-4FEF-82D4-61F48ABDCDE5@clickspace.com>
<29439.1145564220@sss.pgh.pa.us>
<47C1F053-EC91-4AEB-9F0B-B538716145D6@clickspace.com>
<105.1145567988@sss.pgh.pa.us>
<53ACF10A-9240-420B-83AB-E4CBABD2AC56@clickspace.com>
<44482CAF.70309@fuzzy.cz>
<5C372D71-D189-4AA7-A857-1C8FE42311AE@clickspace.com>
On Thu, 20 Apr 2006, Brendan Duddridge wrote:
> Hi Tomas,
>
> Hmm... ktrace -p PID -c returns immediately without doing anything
> unless I've previously done a ktrace -p PID.
>
> According to the man page for ktrace's -c flag:
> -c Clear the trace points associated with the specified file
> or processes.
On other systems, strace/truss with -c produces a list of sys calls with
the number of times they've been called in the elapsed period.
To answer your other question, temporarily disabling fsync during the
recovery should speed it up.
For future reference, processing thousands of WAL files for recovery is
not ideal. You should be doing a base backup much more often.
Gavin
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: swm@alcove.com.au, brendan@clickspace.com, tv@fuzzy.cz
Subject: Re: Recovery will take 10 hours
In-Reply-To: <Pine.LNX.4.58.0604211112400.17115@linuxworld.com.au>
* 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