Re: A bug in recovery prefetcher, triggering asserts / FATAL: checkpoint request failed

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Tomas Vondra <tomas(at)vondra(dot)me>
Cc: surya poondla <suryapoondla4(at)gmail(dot)com>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, shihao zhong <zhong950419(at)gmail(dot)com>
Subject: Re: A bug in recovery prefetcher, triggering asserts / FATAL: checkpoint request failed
Date: 2026-11-20 00:14:18
Message-ID: CAHGQGwF_HdyeO0KFm-5pgMJo9oOJYQMPRB0fnHzNkuNg-0GnKw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 20, 2026 at 8:22 AM Tomas Vondra <tomas(at)vondra(dot)me> wrote:
> What's a good way to check if a machine supports posix_fadvise? I don't
> see any TAP test already doing that. I guess we could try assigning into
> effective_io_concurrency, and skip the test if it fails.

In v18 and later, setting effective_io_concurrency would succeed even on
the platform not supporting posix_fadvise(), such as Windows?
If so, checking recovery_prefetch = on might be a better approach?
Because its check hook, check_recovery_prefetch(), seems to always
return false when USE_PREFETCH is not enabled.

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-11-20 00:17:20 Re: reindexdb: Change quoting rule of --schema?
Previous Message Michael Paquier 2026-11-20 00:01:27 Re: WAL_LOG CREATE DATABASE strategy broken for non-standard page layouts