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

From: Orishich Aleksey <a(dot)orishich(at)cft(dot)ru>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
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-28 02:17:42
Message-ID: 76ead10fde7a4f13b02c5afeeae049b6@cft.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

ОК, what logs do you need?

-----Original Message-----
From: Daniel Gustafsson <daniel(at)yesql(dot)se>
Sent: Tuesday, July 27, 2021 6:58 PM
To: Оришич Алексей Петрович <a(dot)orishich(at)cft(dot)ru>
Cc: 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

> 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

Browse pgsql-bugs by date

  From Date Subject
Next Message Etsuro Fujita 2021-07-28 03:35:29 Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
Previous Message PG Bug reporting form 2021-07-28 01:39:46 BUG #17125: Operator precedence bug in websearch_to_tsquery function