| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Slow PITR restore |
| Date: | 2007-12-12 08:55:24 |
| Message-ID: | 87d4tcjnr7.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> Wow, o.k. well it is something we (the community) really should look at for
> 8.4. I am surprised that it is slower than just walking through the xlogs on
> recovery. I am sure there is a reason just surprised.
Well in the worst case it has to do nearly as much work as the original
database did. And it only gets to use 1 cpu so it can only have one i/o
request pending.
bgwriter is started already when doing recovery, right? Perhaps things could
be helped by telling bgwriter to behave differently during recovery.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian Aumeier | 2007-12-12 09:01:19 | Re: thesaurus support in postgresql |
| Previous Message | Magnus Hagander | 2007-12-12 08:55:13 | Re: Killing a session in windows |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2007-12-12 09:55:49 | Re: [hensa22@yahoo.es: Re: [pgsql-es-ayuda] SLL error 100% cpu] |
| Previous Message | Simon Riggs | 2007-12-12 08:34:09 | Re: WORM and Read Only Tables (v0.1) |