Re: PostgreSQL Service Unable to Start After Archive Log delete

From: Justin <zzzzz(dot)graf(at)gmail(dot)com>
To: loganathan P <plogandba(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org, Oli Sennhauser <oli(dot)sennhauser(at)fromdual(dot)com>
Subject: Re: PostgreSQL Service Unable to Start After Archive Log delete
Date: 2026-09-10 20:56:21
Message-ID: CALL-XeN1Vy4Th6RRwVR7ooSpOYAMx7CaFF8UcNMeJCSReUPaLA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

HI Loganathan,

There is corruption specific to a toasted column index . Do NOT allow the
application to connect to the database. Application will most likely make
the corruption worse if it starts writing to the database

Do a pg_dump if that fails. then start doing pg_dumps one table at a time
to extract what you can.
SELECT * FROM xxxx PosgreSQL will just read the table out without using
indexes.
If you get toast table corruption, SELECT <all columns that are
not toasted> FROM XXXX
If you get table corruption that is to specific data pages then you need
to figure out WHERE clauses to avoid the corrupt datapage.

Can use a page inspector to look at the raw table data to maybe get the
corrupted datapages back or skip the corrupted pages .
https://www.postgresql.org/docs/current/pageinspect.html

>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2026-09-10 21:21:48 Re: PostgreSQL Service Unable to Start After Archive Log delete
Previous Message loganathan P 2026-09-10 20:29:07 Re: PostgreSQL Service Unable to Start After Archive Log delete