I will send as soon as possible. He's running the vacuum yet.

2017-06-05 16:02 GMT-03:00 Adrian Klaver <adrian.kla...@aklaver.com>:

> On 06/05/2017 11:55 AM, tel medola wrote:
>
>> show?
>> /Yes/
>>
>
> Yes, what?
>
> Please run the command as shown:
>
> select * from pg_class where relfilenode = 5214489;
>
> and show the result.
>
>
>> Do not delete the pg_statistic table. I would not even delete from it.
>> /Sorry, I already deleted it. I looked for something official and found
>> in the site in postgres the reference that the delete could be done (
>> https://www.postgresql.org/docs/9.1/static/release-7-4-2.html) and I
>> ended up doing it. Now I'm running a vacuum analyze across the base./
>>
>>
>> 2017-06-05 15:41 GMT-03:00 Adrian Klaver <adrian.kla...@aklaver.com
>> <mailto:adrian.kla...@aklaver.com>>:
>>
>>
>>     On 06/05/2017 07:17 AM, tel medola wrote:
>>
>>         Done.
>>         I followed the steps below after reconnecting the filenode:
>>
>>         Select * from "05122016".repositorio
>>         Count -> 0
>>
>>         Then, I execute the commands:
>>         Analyze "05122016".repositorio;
>>         Count -> 0
>>         Reindex "05122016".repositorio;
>>         Count -> 1509046
>>         Yes!
>>
>>         But...
>>
>>
>>         select * from "05122016".repository where id_documento =
>>         '{A647885D-9738-4617-ACE6-6351F6ADD341}'
>>
>>         Returns the error below:
>>         Missing chunk number 0 for toast value 10259186 in
>> pg_toast_9277966
>>
>>
>>     What does:
>>
>>     select * from pg_class where relfilenode = 5214489;
>>
>>     show?
>>
>>
>>
>>         I read in the forum to run the command:
>>         Delete from pg_statistic;
>>         Reindex table pg_statistic;
>>         Vacuum analyze;
>>
>>         Is it okay to delete the pg_statistic table?
>>
>>
>>     Do not delete the pg_statistic table. I would not even delete from it.
>>
>>     --     Adrian Klaver
>>     adrian.kla...@aklaver.com <mailto:adrian.kla...@aklaver.com>
>>
>>
>>
>
> --
> Adrian Klaver
> adrian.kla...@aklaver.com
>

Reply via email to