From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Bruce Momjian" <bruce(at)momjian(dot)us> |
Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Add URLs for : * Speed WAL recovery by allowing more than one |
Date: | 2008-03-18 20:06:24 |
Message-ID: | 874pb3lrun.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
"Bruce Momjian" <bruce(at)momjian(dot)us> writes:
>> > > On Tue, 2008-03-18 at 03:59 +0000, Bruce Momjian wrote:
>> > > > * Speed WAL recovery by allowing more than one page to be prefetched
>> > > >
>> > > > This involves having a separate process that can be told which pages
>> > > > the recovery process will need in the near future.
>
> Are you reading the same thread I am? See:
>
> http://archives.postgresql.org/pgsql-hackers/2008-02/msg01301.php
I don't think there's any consensus for the approach you describe above. If
anything it seemed the least objectionable form was something involving
posix_fadvise or libaio.
Tom did wave us off from Simon's approach on the basis of it being hard to
test and Heikki seemed to be agreeing on the basis that it would be better to
reuse infrastructure useful in other cases as well. So I guess that's some
kind of consensus... of two.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2008-03-18 20:56:13 | Re: pgsql: Add URLs for : * Speed WAL recovery by allowing more than one |
Previous Message | Bruce Momjian | 2008-03-18 18:40:42 | pgsql: Add to TODO: > > * Consider not storing a NULL bitmap on disk |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2008-03-18 20:56:13 | Re: pgsql: Add URLs for : * Speed WAL recovery by allowing more than one |
Previous Message | Denis Vnukov @ Nabble | 2008-03-18 19:17:39 | Problems with compilation of user-defined C functions for PostgreSQL 8.3.0 |