| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | rootcause000(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18090: Encountering Toast Table Corruption and Missing Chunk Number Error During PostgreSQL Data Migration |
| Date: | 2023-09-06 08:08:06 |
| Message-ID: | 32191696d0601ff313e4da17b7756a89391a8ba5.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2023-09-06 16:57:01 | Re: BUG #18046: stats collection behaviour change is affecting the usability of information. |
| Previous Message | Lepikhov Andrei | 2023-09-06 07:14:40 | Re: BUG #18077: PostgreSQL server subprocess crashed by a SELECT statement with WITH clause |