Re: BUG #18088: Table Corruption Issues Arising from Abrupt Server Shutdown During PostgreSQL 10.20 to 14.7 Migratio

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: rootcause000(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18088: Table Corruption Issues Arising from Abrupt Server Shutdown During PostgreSQL 10.20 to 14.7 Migratio
Date: 2023-09-05 17:44:40
Message-ID: CAKFQuwbv6R4-GVE9MgafeZp14Hy02nXPsX1pL73HgP3vimz3oQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Sep 5, 2023 at 7:02 AM PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:

> The following bug has been logged on the website:
>
> Bug reference: 18088
> Logged by: Root Cause
> Email address: rootcause000(at)gmail(dot)com
> PostgreSQL version: Unsupported/Unknown
> Operating system: Microsoft Windows Server 2019 Standard
> Description:
>
> Please advise if there are alternative methods to recover the data and if
> there are options to prevent this issue from occurring even in the event of
> an abrupt server shutdown.
>

There is likely no bug here - improper configuration or bad hardware is
about the only time an improper shutdown is going to cause data loss. The
WAL-based recovery system (which is also usable/required for backups)
accommodates abrupt server shutdowns just fine.

Please use the -general or -admin lists if you wish to further discuss how
to inspect just how your system may be misconfigured and for any guidance
on correcting your lack of backups.

David J,

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2023-09-05 20:23:45 BUG #18090: Encountering Toast Table Corruption and Missing Chunk Number Error During PostgreSQL Data Migration
Previous Message Bruce Momjian 2023-09-05 15:18:52 Re: BUG #18084: Count Mismatch Challenges During PostgreSQL Database Migration: Causes and Solutions