Re: could not extend file "base/5/3501" with FileFallocate(): Interrupted system call

From: Christoph Berg <myon(at)debian(dot)org>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: could not extend file "base/5/3501" with FileFallocate(): Interrupted system call
Date: 2023-04-25 18:24:30
Message-ID: ZEga3qnXMHLzRZ+v@msg.df7cb.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Re: Andres Freund
> A prototype of that approach is attached. I pushed the retry handling into the
> pg_* routines where applicable. I guess we could add pg_* routines for
> FileFallocate(), FilePrewarm() etc as well, but I didn't do that here.
>
> Christoph, could you verify this fixes your issue?

Everything green with the patch applied. Thanks!

https://pgdgbuild.dus.dg-i.net/job/postgresql-16-binaries-snapshot/839/

Christoph

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2023-04-25 22:18:04 pgsql: Re-add tracking of wait event SLRUFlushSync
Previous Message Daniel Gustafsson 2023-04-25 12:00:03 pgsql: Fix vacuum_cost_delay check for balance calculation.

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2023-04-25 18:39:14 Re: pg_stat_io for the startup process
Previous Message Melanie Plageman 2023-04-25 17:54:43 Re: pg_stat_io for the startup process