From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Koichi Suzuki <koichi(dot)szk(at)gmail(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Proposal of PITR performance improvement for 8.4. |
Date: | 2008-10-28 11:38:57 |
Message-ID: | 1225193937.3971.162.camel@ebony.2ndQuadrant |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2008-10-28 at 16:33 +0900, Koichi Suzuki wrote:
> This is my first proposal of PITR performance improvement for
> PostgreSQL 8.4 development. This proposal includes readahead
> mechanism of data pages which will be read by redo() routines in the
> recovery. This is especially effective in the recovery without full
> page write. Readahead is done by posix_fadvise() as proposed in
> index scan improvement.
>
> Details of the implementation will be found in README file in the material.
I'm happy with the idea of a readahead process. I thought we were
implementing a BackgroundReader process for other uses. Is that dead
now?
I see you're doing this as a standalone command. Shame we can't include
this into core for now, but I can see the reasons why.
How does the whole toolchain look with this?
Can you give a simple example of using pg_lesslog, pg_readahead and
pg_standby together, if that is appropriate?
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2008-10-28 12:02:48 | Re: VACUUMs and WAL |
Previous Message | Simon Riggs | 2008-10-28 11:25:08 | Re: Visibility map, partial vacuums |