Re: BUG #18090: Encountering Toast Table Corruption and Missing Chunk Number Error During PostgreSQL Data Migration

Поиск
Список
Период
Сортировка
От Laurenz Albe
Тема Re: BUG #18090: Encountering Toast Table Corruption and Missing Chunk Number Error During PostgreSQL Data Migration
Дата
Msg-id 32191696d0601ff313e4da17b7756a89391a8ba5.camel@cybertec.at
обсуждение исходный текст
Ответ на BUG #18090: Encountering Toast Table Corruption and Missing Chunk Number Error During PostgreSQL Data Migration  (PG Bug reporting form <noreply@postgresql.org>)
Список pgsql-bugs
On Tue, 2023-09-05 at 20:23 +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference:      18090
> Logged by:          Root Cause
> Email address:      rootcause000@gmail.com
> PostgreSQL version: Unsupported/Unknown
> Operating system:   Microsoft Windows Server 2019 Standard
> Description:       
>
> Version - PostgreSQL 10.21, compiled by Visual C++ build 1800, 64-bit
>
> Platform - Windows
>
> When migrating data from PostgreSQL 10.21 to 14.7, we encountered an issue
> during the dump process related to table corruption, resulting in the error
> message 'could not open file "base/16510/37857": No such file or
> directory.'
>
> ERROR: could not open file "base/16510/37857": No such file or directory

Where is the PostgreSQL bug you want to report?
If you want to claim that PostgreSQL removed the file behind that table,
you need some evidence.

Yours,
Laurenz Albe



В списке pgsql-bugs по дате отправления:

Предыдущее
От: "Lepikhov Andrei"
Дата:
Сообщение: Re: BUG #18077: PostgreSQL server subprocess crashed by a SELECT statement with WITH clause
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: BUG #18046: stats collection behaviour change is affecting the usability of information.