From: | Torsten Krah <krah(dot)tm(at)gmail(dot)com> |
---|---|
To: | Slava Shpitalny <slava(dot)shpitalny(at)tactilemobility(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: could not open file "base/XX/XX": Interrupted system call |
Date: | 2025-01-13 09:34:46 |
Message-ID: | f5ded01078e8e50374393761e0a48fbd7adf6f4a.camel@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Divyansh Gupta JNsThMAudy | 2025-01-13 12:29:52 | Need help in logical replication |
Previous Message | Enrico Schenone | 2025-01-13 08:45:53 | Re: Intermittent errors when fetching cursor rows on PostgreSQL 16 |