Re: Redo the filenode link in tablespace

From: tel medola <tel(dot)medola(at)gmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Redo the filenode link in tablespace
Date: 2017-06-05 12:24:53
Message-ID: CANRMYmhUmVkxmncDXWyCzyecnzZfJzDZPbDMBTgVCJ+cH=iy5w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Sorry. I got sick these days and could not read my emails.

Thanks for your help.
I'll try to point to the direct node and see what happens.

2017-06-01 10:29 GMT-03:00 Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>:

> On 06/01/2017 03:47 AM, tel medola wrote:
>
>> Did you get any help with this?
>> /I formatted correctly before sending the email. Maybe you should ask
>> yourself if the mail server did not remove the formatting./
>>
>
> I was talking about help with your relfilenode issue, I learned to deal
> with the formatting awhile ago.
>
> /
>> /
>> Well the relpages, reltuples are estimated values that can be updated
>> with an ANALYZE./
>> /
>>
>> /I can not make analyze on a table whose filenode is pointing to another
>> reference. The table is empty, just because the filenode does not point to
>> the correct ID./
>>
>
> Understood, I was just saying that if you could get the table pointing at
> the right relfilenode the other values would be synced up with an ANALYZE.
>
> At this point it is time to just try something. You have file level
> backups of the various backups, so you can restore that if something goes
> wrong, correct?
>
> For 01052016.repositorio with current pg_class entry of relfilenode of
> 13741352, change that back to the old entry of 5214489.
>
>
>
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message tel medola 2017-06-05 14:17:45 Re: Redo the filenode link in tablespace
Previous Message Garry Sim 2017-06-05 10:14:27 Unable to install EASM postgre due to error 8023