Re: Urgent !!!! Tables inaccessible postgres v17.6

From: Licio Matos <licio(dot)matos(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: mahamood hussain <hussain(dot)ieg(at)gmail(dot)com>, Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Urgent !!!! Tables inaccessible postgres v17.6
Date: 2026-08-07 22:07:57
Message-ID: CAK6Tc4Op4=pD2ZL2AS789j+=Tx7MbRnzBzFf7BBWFrmeC+Cw0A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Have you try to check these blocks are table related or index related?

You are counting, could be a index corrupted.

Try this:

SELECT relname, relkind
FROM pg_class
WHERE pg_relation_filepath(oid) LIKE '%447758%';

Licio Matos

Em sex., 7 de ago. de 2026 às 18:56, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
escreveu:

> On Thu, 2026-08-06 at 19:57 +0530, mahamood hussain wrote:
> > The database is hosted on Azure Premium SSD v2, using four striped disks.
> >
> > >
> > > > prod=# SELECT count(*) FROM schema.tablename;
> > > >
> > > > WARNING: page verification failed, calculated checksum 50897 but
> expected 50048
> > > > ERROR: invalid page in block 696770 of relation base/16388/447758
>
> Looks like Microsoft's storage is not reliable.
>
> Yours,
> Laurenz Albe
>
>
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Koen De Groote 2026-08-08 15:06:05 Re: PostgreSQL 14 standby recovery stuck in archive recovery state
Previous Message Laurenz Albe 2026-08-07 21:56:00 Re: Urgent !!!! Tables inaccessible postgres v17.6