Re: WAL prefetch - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: WAL prefetch
Date
Msg-id 638f556a-ef64-9191-1e16-06ab7ff4b1ce@2ndquadrant.com
Whole thread Raw
In response to Re: WAL prefetch  (Andres Freund <andres@anarazel.de>)
Responses Re: WAL prefetch
Re: WAL prefetch
List pgsql-hackers

On 06/15/2018 08:01 PM, Andres Freund wrote:
> On 2018-06-14 10:13:44 +0300, Konstantin Knizhnik wrote:
>>
>>
>> On 14.06.2018 09:52, Thomas Munro wrote:
>>> On Thu, Jun 14, 2018 at 1:09 AM, Konstantin Knizhnik
>>> <k.knizhnik@postgrespro.ru> wrote:
>>>> pg_wal_prefetch function will infinitely traverse WAL and prefetch block
>>>> references in WAL records
>>>> using posix_fadvise(WILLNEED) system call.
>>> Hi Konstantin,
>>>
>>> Why stop at the page cache...  what about shared buffers?
>>>
>>
>> It is good question. I thought a lot about prefetching directly to shared
>> buffers.
> 
> I think that's definitely how this should work.  I'm pretty strongly
> opposed to a prefetching implementation that doesn't read into s_b.
> 

Could you elaborate why prefetching into s_b is so much better (I'm sure 
it has advantages, but I suppose prefetching into page cache would be 
much easier to implement).

regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: ON CONFLICT DO NOTHING on pg_dump
Next
From: Thomas Munro
Date:
Subject: Re: WAL prefetch