| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Jeff Trout" <threshar(at)real(dot)jefftrout(dot)com> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Slow PITR restore |
| Date: | 2007-12-12 18:02:39 |
| Message-ID: | 87r6hr3i68.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
"Jeff Trout" <threshar(at)torgo(dot)978(dot)org> writes:
> On Dec 12, 2007, at 11:29 AM, Joshua D. Drake wrote:
>
>> 8 seconds for a single archive recovery is very slow in consideration of
>> this machine. Even single threaded that seems slow.
>
> I've seen this on my PITR restores (thankfully, they were for fetching some
> old data, not because we expoded). On a 2.4ghz opteron it took 5-50 seconds
> per wal segment,
I'm not sure what you guys' expectations are, but if you're restoring 5
minutes worth of database traffic in 8 seconds I wouldn't be complaining.
Depending on your transaction mix and what percentage of it is read-only
select queries you might reasonably expect the restore to take as long as it
took to generate them...
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2007-12-12 18:08:08 | Re: Slow PITR restore |
| Previous Message | Ron Mayer | 2007-12-12 18:00:19 | Re: top posting |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2007-12-12 18:08:08 | Re: Slow PITR restore |
| Previous Message | Tom Lane | 2007-12-12 17:56:04 | Re: Slow PITR restore |