Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #18088: Table Corruption Issues Arising from Abrupt Server Shutdown During PostgreSQL 10.20 to 14.7 Migratio - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #18088: Table Corruption Issues Arising from Abrupt Server Shutdown During PostgreSQL 10.20 to 14.7 Migratio
Date
Msg-id CAKFQuwbv6R4-GVE9MgafeZp14Hy02nXPsX1pL73HgP3vimz3oQ@mail.gmail.com
Whole thread Raw
In response to BUG #18088: Table Corruption Issues Arising from Abrupt Server Shutdown During PostgreSQL 10.20 to 14.7 Migratio  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
Tree view
On Tue, Sep 5, 2023 at 7:02 AM PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      18088
Logged by:          Root Cause
Email address:      rootcause000@gmail.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,

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: BUG #18084: Count Mismatch Challenges During PostgreSQL Database Migration: Causes and Solutions
Next
From: PG Bug reporting form
Date:
Subject: BUG #18090: Encountering Toast Table Corruption and Missing Chunk Number Error During PostgreSQL Data Migration