Re: BUG #16881: error log:Npgsql.PostgresException (0x80004005): XX001: 无法读取文件"base/16394/25021"的块157:只读取了8192字节的0

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: 孙宇森 <sun623227787(at)qq(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16881: error log:Npgsql.PostgresException (0x80004005): XX001: 无法读取文件"base/16394/25021"的块157:只读取了8192字节的0
Date: 2021-02-24 12:07:35
Message-ID: CAOBaU_Y0tS8_Xk_0XWKaFHG12rOkN1pzC69MQZ4yUnLsfC0rMw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

Please keep the mailing list in Cc, and please don't top post.

On Wed, Feb 24, 2021 at 5:34 PM 孙宇森 <sun623227787(at)qq(dot)com> wrote:
>
> Only this error log.

Really, there wasn't any additional line with "STATEMENT:" or "HINT:" nearby?

> I tried to scan the disk and found no bad path; I tried
> to query for deadlock, the sentence is as follows: select * from PG_ stat_
> Activity where datname ='cms'; as a result, there is no deadlock process.
> "wait_event_type"and"wait_event" is null.

You likely won't see any sign of that problem in pg_stat_activity.
Can you connect to the target database (I'm assuming "cms") and run
this query:

SELECT relname FROM pg_class WHERE relfilenode = 25021;

This will give you the name of the affected relation. If that's a
table you can check doing a "SELECT * FROM the_table" to see if the
problem is still there or not. Otherwise just rebuild the index or
recreate the materialized view. Be careful, the above query will only
give you an unqualified relation name, if you have multiple schema
containing the same object names, check in the catalogs to see which
schema should be used.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Антон Курочкин 2021-02-24 12:22:56 Re: BUG #16894: PANIC: WAL contains references to invalid pages
Previous Message PG Bug reporting form 2021-02-24 11:34:23 BUG #16895: Multicolumn GiST index returns incomplete results