Re: Recovery will take 10 hours - Mailing list pgsql-performance

From Simon Riggs
Subject Re: Recovery will take 10 hours
Date
Msg-id 1145899652.3112.326.camel@localhost.localdomain
Whole thread Raw
In response to Re: Recovery will take 10 hours  (Brendan Duddridge <brendan@clickspace.com>)
List pgsql-performance
On Sun, 2006-04-23 at 22:46 -0600, Brendan Duddridge wrote:

> So how do you overlap the restore process with the retrieving of files?

The restore command can be *anything*. You just write a script...

> Our restore command is:
>
> restore_command = 'gunzip </wal_archive/%f.gz>%p'
>
> If I change it to:
>
> restore_command = 'gunzip </wal_archive/%f.gz>%p &'
>
> to execute the restore command in the background, will that do the
> trick?

No, but you can execute a shell script that does use & internally.

> But I don't think the real problem was the retrieval of the files. It
> only
> took maybe 1/2 a second to retrieve the file, but often took anywhere
> from
> 5 to 30 seconds to process the file. More so on the longer end of the
> scale.

Sorry, thought you meant the decompression time.

--
  Simon Riggs
  EnterpriseDB          http://www.enterprisedb.com/


pgsql-performance by date:

Previous
From: Markus Schaber
Date:
Subject: Re: Recovery will take 10 hours
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Slow deletes in 8.1 when FKs are involved