On Mon, 2009-03-16 at 12:11 -0400, Mark Steben wrote:
> First of all, I did pose this question first on the pgsql – admin
> mailing list.
> The issue is that during a restore on a remote site, (Postgres 8.2.5)
> archived logs are taking an average of 35 – 40 seconds apiece to
Archive logs are restored in a serialized manner so they will be slower
to restore in general.
Joshua D. Drake
PostgreSQL - XMPP:
Consulting, Development, Support, Training
503-667-4564 - http://www.commandprompt.com/
The PostgreSQL Company, serving since 1997
Joshua D. Drake wrote:
> On Mon, 2009-03-16 at 12:11 -0400, Mark Steben wrote:
>> The issue is that during a restore on a remote site, (Postgres 8.2.5)
8.2.5 is quite old. You should upgrade to the latest 8.2.X release.
>> archived logs are taking an average of 35 – 40 seconds apiece to
> Archive logs are restored in a serialized manner so they will be slower
> to restore in general.
Yeah, if you have several concurrent processes on the primary doing I/O
and generating log, at restore the I/O will be serialized.
Version 8.3 is significantly better with this (as long as you don't
disable full_page_writes). In earlier versions, each page referenced in
the WAL was read from the filesystem, only to be replaced with the full
page image. In 8.3, we skip the read and just write over the page image.
Depending on your application, that can make a very dramatic difference
to restore time.
Your message is accepted. The reference number is .