On Fri, Dec 20, 2024 at 01:25:41PM +0100, Jakub Wartak wrote:
> On Thu, Dec 19, 2024 at 7:49 AM Michael Harris <harmic@gmail.com> wrote:
> No one else has responded, so I'll try. My take is that we got very limited
> number of reports (2-3) of this stuff happening and it always seem to be >90%
> space used, yet the adoption of PG16 is rising, so we may or may not see more
> errors of those kind, but on another side of things: it's frequency is so rare
My guess is that if you are seeing this with 90% full, and not lesser
values, that something is being temporarily exhausted in XFS and the
kernel errno API just doesn't allow returning enough detail to explain
what is being exhausted. A traditional Unix file system only has limits
for the inode table and free blocks, but I am sure XFS has many more
areas of possible exhaustion.
I didn't see any mention of checking the kernel log, which might have
more details of what XFS is having problems with.
I agree trying to modify Postgres for this now makes no sense since we
don't even know the cause. Once we find the cause, and admit it can't
be avoided or quickly fixed, we can reevaluate.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
