Re: could not open file "base/XX/XX": Interrupted system call - Mailing list pgsql-general

From Torsten Krah
Subject Re: could not open file "base/XX/XX": Interrupted system call
Date
Msg-id f5ded01078e8e50374393761e0a48fbd7adf6f4a.camel@gmail.com
Whole thread Raw
In response to Re: could not open file "base/XX/XX": Interrupted system call  (Slava Shpitalny <slava.shpitalny@tactilemobility.com>)
List pgsql-general
Am Donnerstag, dem 26.12.2024 um 13:48 +0200 schrieb Slava Shpitalny:
> Do you happen to have any updates on this issue?

Hi,

unfortunately not, the only thing I found is this in "man 2 open":

...

EINTR  While blocked waiting to complete an open of a slow device
(e.g., a FIFO; see fifo(7)), the call was interrupted by a signal
handler; see signal(7).
...


To me this reads that postgres should handle that error code (e.g. try
again n times before failing) - but maybe it does that already, I did
not verify all open calls, if or how postgres does handle EINTR.

The only thing I did change is, that I use a volume (an anonymous one
in my usecase) again, because with that, I never encountered that error
- if I omit that volume and write directly to the containers fs (which
would be sufficient for me), I still had that error.

kind regards

Torsten




pgsql-general by date:

Previous
From: Isaac Morland
Date:
Subject: Re: Automatic upgrade of passwords from md5 to scram-sha256
Next
From: nicolas
Date:
Subject: pg_repack and locks