Message-ID: <f5ded01078e8e50374393761e0a48fbd7adf6f4a.camel@gmail.com>
Subject: Re: could not open file "base/XX/XX": Interrupted system call
From: Torsten Krah <krah.tm@gmail.com>
To: Slava Shpitalny <slava.shpitalny@tactilemobility.com>
Cc: pgsql-general@lists.postgresql.org
Date: Mon, 13 Jan 2025 10:34:46 +0100
In-Reply-To: <CA+DMLeKxsOApczjoXz_dxJiXtWiHMPzEOf_ZPQ=cFJxoCdGhwg@mail.gmail.com>
References: <c15876f7330705cc5e1ba7935b4af8ed1367fd47.camel@gmail.com>
	 <4c859b7d424698b54d617bd888e30ca37d19304b.camel@cybertec.at>
	 <2159f2f698521b0be92ef44e3656edaf72a380f3.camel@gmail.com>
	 <CA+DMLeKxsOApczjoXz_dxJiXtWiHMPzEOf_ZPQ=cFJxoCdGhwg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.44.4-0ubuntu2 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/f5ded01078e8e50374393761e0a48fbd7adf6f4a.camel%40gmail.com>
Precedence: bulk

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