Message-ID: <5babe0a94e3c7e6010e2e7de799745b16a31ecfa.camel@cybertec.at>
Subject: Re: PostgreSQL Service Unable to Start After Archive Log delete
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: loganathan P <plogandba@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Date: Thu, 10 Sep 2026 23:26:03 +0200
In-Reply-To: 
 <CAFX4Q9KhtvVcSPsEZ=Z2HvV+yUE50xopfrgGEeFL_iE=Ye8kVg@mail.gmail.com>
References: 
	<CAFX4Q9+z686bXOLuxd1pQ7nLCPVFAhLJwVy7qDbtQA5y8i+D8g@mail.gmail.com>
	 <71577a48d543192c8e74af490238b0c3f9da9500.camel@cybertec.at>
	 <CAFX4Q9KhtvVcSPsEZ=Z2HvV+yUE50xopfrgGEeFL_iE=Ye8kVg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.60.2 (3.60.2-1.fc44) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/5babe0a94e3c7e6010e2e7de799745b16a31ecfa.camel%40cybertec.at>
Precedence: bulk

On Thu, 2026-09-10 at 19:47 +0530, loganathan P wrote:
> Backups are available only for 10-Sep-2026 at 02:00 AM IST.
> Please let us know if any alternative solution is available.

There is no good alternative to restoring your backup.
Particularly if you are not a PostgreSQL expert.

> The issue occurred on 10-Sep-2026 at 11:00 AM IST.

Count yourself lucky.  You are only losing 9 hours of data.
That's better than staying down for days in a desperate attempt to
fix the data loss in some other fashion.

In the future, you should use a better backup strategy that allows
point-in-time-recovery to reduce the data loss.

Yours,
Laurenz Albe