Re: Read-ahead and parallelism in redo recovery - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Read-ahead and parallelism in redo recovery
Date
Msg-id 12563.1204318035@sss.pgh.pa.us
Whole thread Raw
In response to Re: Read-ahead and parallelism in redo recovery  (Decibel! <decibel@decibel.org>)
Responses Re: Read-ahead and parallelism in redo recovery  (Aidan Van Dyk <aidan@highrise.ca>)
List pgsql-hackers
Decibel! <decibel@decibel.org> writes:
> Perhaps a good short-term measure would be to have recovery allocate  
> a 16M buffer and read in entire xlog files at once.

If that isn't entirely useless, you need a better kernel.  The system
should *certainly* be bright enough to do read-ahead for our reads of
the source xlog file.  The fetches that are likely to be problematic are
the ones for pages in the data area, which will be a lot less regular
for typical workloads.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Heikki Linnakangas"
Date:
Subject: Re: Read-ahead and parallelism in redo recovery
Next
From: Aidan Van Dyk
Date:
Subject: Re: Read-ahead and parallelism in redo recovery