Re: could not open file "base/XX/XX": Interrupted system call

From: Slava Shpitalny <slava(dot)shpitalny(at)tactilemobility(dot)com>
To: krah(dot)tm(at)gmail(dot)com
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: could not open file "base/XX/XX": Interrupted system call
Date: 2024-12-26 11:48:59
Message-ID: CA+DMLeKxsOApczjoXz_dxJiXtWiHMPzEOf_ZPQ=cFJxoCdGhwg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.
The table is a big one (related to
https://www.postgresql.org/message-id/16832-943d33fd58eb26e4%40postgresql.org
)

Do you happen to have any updates on this issue?

*Slava Shpitalny*

Software Development Team Lead

Tactile Mobility

E-mail: slava(dot)shpitalny(at)tactilemobility(dot)com

On Thu, Dec 26, 2024 at 1:43 PM Torsten Krah <krah(dot)tm(at)gmail(dot)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
>
>
>
>
>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message PetSerAl 2024-12-26 17:40:44 Synchronous commit after asynchronous commit
Previous Message Adrian Klaver 2024-12-25 23:20:38 Re: Intermittent errors when fetching cursor rows on PostgreSQL 16