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

From Slava Shpitalny
Subject Re: could not open file "base/XX/XX": Interrupted system call
Date
Msg-id CA+DMLeKxsOApczjoXz_dxJiXtWiHMPzEOf_ZPQ=cFJxoCdGhwg@mail.gmail.com
Whole thread Raw
In response to Re: could not open file "base/XX/XX": Interrupted system call  (Torsten Krah <krah.tm@gmail.com>)
List pgsql-general
Hi,
We are facing a similar problem using a docker from https://hub.docker.com/_/postgres on AWS EC2 machine.
The version we are using is 17 (docker image "postgres:17")
The issue happens on our CI server, and it happens consistently.

Do you happen to have any updates on this issue?

Slava Shpitalny

Software Development Team Lead

Tactile Mobility

E-mail: slava.shpitalny@tactilemobility.com




On Thu, Dec 26, 2024 at 1:43 PM Torsten Krah <krah.tm@gmail.com> wrote:
Am Mittwoch, dem 20.09.2023 um 13:11 +0200 schrieb Laurenz Albe:
> Is that an NFS mount?  What are the mount options?
>
> Yours,
> Laurenz Albe

No mount at all.

Just the docker container filesystem using the overlay2 storage driver,
there is nothing externally mounted in that container, the data is
already in the image (via docker COPY) from which the container gets
created (and that data directory was created in the image build process
via pg_restore from the dump file).

The whole container / image just involves overlay2 fs which itself is
sitting on ext4.

Torsten





pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Intermittent errors when fetching cursor rows on PostgreSQL 16
Next
From: PetSerAl
Date:
Subject: Synchronous commit after asynchronous commit