From: | Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | friend(dot)have_00(at)icloud(dot)com, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Could not read block 0 in file |
Date: | 2022-04-08 10:22:07 |
Message-ID: | CAM+6J97MtEXFkEW4KC=H7VgUMSZXDbKRT+Hz1P1izsQ43MWq0A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 8 Apr 2022 at 15:31, Vijaykumar Jain <
vijaykumarjain(dot)github(at)gmail(dot)com> wrote:
>
>
> On Fri, 8 Apr 2022 at 15:24, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>
>>
>>
>> On Fri, Apr 8, 2022 at 11:06 AM <friend(dot)have_00(at)icloud(dot)com> wrote:
>>
>>> Hi,
>>>
>>> While we are looking for a suitable backup to recover from, I hope this
>>> community may have some other advice on forward steps in case we cannot
>>> restore.
>>>
>>> RCA: Unexpected shutdown due to critical power failure
>>>
>>> Current Issue: The file base/16509/17869 is zero bytes in size.
>>>
>>> The error message when running this query is:
> ERROR: could not read block 0 in file "base/16509/17869": read only 0 of
> 8192 bytes
>
> i guess it is maybe page header/ metadata not the whole file is zero
> bytes. the data can be recovered then from the blogs?
> i may be corrected :)
>
>
My bad, sorry did not read the email properly.
*The file does exist on the file system, with zero bytes, as do the
associated fsm and vm files.*
As Magnus suggests, then.
--
Thanks,
Vijay
LinkedIn - Vijaykumar Jain
<https://www.linkedin.com/in/vijaykumarjain/>
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2022-04-08 11:00:13 | Re: Support logical replication of DDLs |
Previous Message | Ron | 2022-04-08 10:01:24 | Re: Could not read block 0 in file |