Re: WIP: WAL prefetch (another approach) - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: WIP: WAL prefetch (another approach)
Date
Msg-id 03cf0942-662b-8ef5-90e4-b8182f2e1b8d@enterprisedb.com
Whole thread Raw
In response to Re: WIP: WAL prefetch (another approach)  (Simon Riggs <simon.riggs@enterprisedb.com>)
Responses Re: WIP: WAL prefetch (another approach)  (Simon Riggs <simon.riggs@enterprisedb.com>)
List pgsql-hackers
On 4/12/22 15:58, Simon Riggs wrote:
> On Thu, 7 Apr 2022 at 08:46, Thomas Munro <thomas.munro@gmail.com> wrote:
> 
>> With that... I've finally pushed the 0002 patch and will be watching
>> the build farm.
> 
> This is a nice feature if it is safe to turn off full_page_writes.
> 
> When is it safe to do that? On which platform?
> 
> I am not aware of any released software that allows full_page_writes
> to be safely disabled. Perhaps something has been released recently
> that allows this? I think we have substantial documentation about
> safety of other settings, so we should carefully document things here
> also.
> 

I don't see why/how would an async prefetch make FPW unnecessary. Did
anyone claim that be the case?


regards

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: random() function documentation
Next
From: Simon Riggs
Date:
Subject: Re: WIP: WAL prefetch (another approach)