* Pavan Deolasee: > The current redo-recovery is a single threaded, synchronous process. > The XLOG is read sequentially, each log record is examined and > replayed if required. This requires reading disk blocks in the > shared buffers and applying changes to the buffer. The reading > happens synchronously and that would usually make the redo process > very slow.
Are you sure that it's actually slow for that reason? Sequential I/O on the log is typically quite fast, and if the pages dirtied since the last checkpoint fit into the cache (shared buffers or OS cache), even that part of recovery does not result in lots of random I/O (with 8.3 and full page writes active; this is a relatively recent change). In the end, I wouldn't be surprised if for most loads, cache warming effects dominated recovery times, at least when the machine is not starved on RAM. -- Florian Weimer <[EMAIL PROTECTED]> BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99 ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
