Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed

Поиск
Список
Период
Сортировка
От Tatsuki Kadomoto
Тема Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed
Дата
Msg-id u537pwebckiob3m5oyag7wo0.1472170180957@email.android.com
обсуждение исходный текст
Ответ на Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed  (Michael Paquier <michael.paquier@gmail.com>)
Ответы Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed  (Michael Paquier <michael.paquier@gmail.com>)
Список pgsql-general
Michael,

In my case, it only detected once.
Does Postgre have any mechanism to correct the mapping file automatically?

Regards,
Tatsuki

Sent from my ASUS


-------- オリジナルのメッセージ --------
送信元:Michael Paquier
送信済み:Fri, 26 Aug 2016 09:05:53 +0900
送信先:Tatsuki Kadomoto
Cc:Kevin Grittner ,John R Pierce ,PostgreSQL mailing lists
件名:Re: [GENERAL] incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed

On Thu, Aug 25, 2016 at 9:48 PM, Tatsuki Kadomoto
<tatsuki.kadomoto@proceranetworks.com> wrote:
> Does this mean it's a kind of expected to face checksum error when the mapping file is relocated by VACUUM FULL?
> I faced the checksum error exactly when VACUUM FULL was running and it has never been detected until now.

No, it's not. This should not happen. And this means that your data
folder is facing some corruption.
--
Michael

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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed
Следующее
От: Ahsan Ali
Дата:
Сообщение: Re: LOG: could not fork new process for connection: Cannot allocate memory