Re: Postgresql12: ERROR: Could not read from file "pg_act/02 F 4" at offset 253952: read too few bytes

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Orishich Aleksey <a(dot)orishich(at)cft(dot)ru>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Postgresql12: ERROR: Could not read from file "pg_act/02 F 4" at offset 253952: read too few bytes
Date: 2021-07-27 11:58:19
Message-ID: C57F6B62-5509-46AD-84B7-50F14CC4EDFB@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 27 Jul 2021, at 13:38, Orishich Aleksey <a(dot)orishich(at)cft(dot)ru> wrote:

> Do you have a result on my problem?

Troubleshooting why a file on your filesystem was corrupt/torn after the fact
when no logs or traces of evidence exists is next to impossible. In this case
there isn't even an errno set from the system. A good place to start would be
to upgrade your system as you are several bugfix releases behind.

> This is critical for us.

The PostgreSQL website lists several professional services companies who offer
support contracts with SLA's which this list doesn't, and who can be hands-on
to investigate should this ever happen again.

--
Daniel Gustafsson https://vmware.com/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrey Borodin 2021-07-27 12:50:55 Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data
Previous Message Orishich Aleksey 2021-07-27 11:38:20 RE: Postgresql12: ERROR: Could not read from file "pg_act/02 F 4" at offset 253952: read too few bytes