On Wed, 2007-12-12 at 08:55 +0000, Gregory Stark wrote: > "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. It's the same speed because it is the same recovery code. > 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. That need only be slow in certain circumstances. > bgwriter is started already when doing recovery, right? Perhaps things could > be helped by telling bgwriter to behave differently during recovery. It would certainly help if bgwriter came up earlier. I've been looking at that just recently. The main issue is how to structure the code to tell bgwriter when it can start processing in recovery mode and then move into normal mode. -- Simon Riggs 2ndQuadrant http://www.2ndQuadrant.com ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
