Re: Damaged (during upgrade?) table, how to repair? - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Damaged (during upgrade?) table, how to repair?
Date
Msg-id fddafac2-f811-4c31-76af-f8f04e014d18@aklaver.com
Whole thread Raw
In response to Re: Damaged (during upgrade?) table, how to repair?  ("W.P." <laurentp@wp.pl>)
Responses Re: Damaged (during upgrade?) table, how to repair?  ("W.P." <laurentp@wp.pl>)
List pgsql-general
On 7/1/21 9:24 PM, W.P. wrote:
> W dniu 01.07.2021 o 22:27, Adrian Klaver pisze:
>> On 7/1/21 12:56 PM, W.P. wrote:
>>> W dniu 01.07.2021 o 16:19, Laurenz Albe pisze:
>>>> On Thu, 2021-07-01 at 10:56 +0200, W.P. wrote:
>>>>> I have a PG 11.12 (was 9.5 or 9.5) upgraded from 9.x (during OS 
>>>>> upgrade).
>>>>>
>>>>> One table is now damaged, trying to dump it results in server restart,
>>>>> message is "invalid record length xxxx maximum is yyy" (from memory).
>>>>>
>>>>> How can I (?) repair this table? (for recent data this works OK).
>>>> If you have a backup, take that.
>>>>
>>>> If not, hire an expert in data recovery.
>>>>
>>>> Yours,
>>>> Laurenz Albe
>>>
>>> I have something similar to backup: old database, but it is 9.5, how 
>>> can I install 9.5 binaries / libs / config on Fedora 30 i386 (with 
>>> PG11 installed) side-by-side?
>>
>> Is the old database on another machine where it can be started and 
>> then the data dumped?
>>
> It is on another disc, with OS that has problems (F24 does not boot 
> beyond single user mode, Network Manager doesn't start) after removing 
> power / battery while in "suspend to RAM".
> 
> Thats why I think about setting 9.5 on my current machine (F30/PG11 
> cluster) and then do a dump, only I need to know how to do it (binaries 
> / libs / default cfg + data copy).
> 

So you have backup of the failed machine's disk stored somewhere else?

Otherwise how are you going to get the 9.5 instance to the new machine?


> 
> Laurent
> 
> 
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

Previous
From: Igor Korot
Date:
Subject: Re:
Next
From: Tom Lane
Date:
Subject: