"Joshua D. Drake" <jd@xxxxxxxxxxxxxxxxx> 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! ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
