| From: | Tatsuki Kadomoto <tatsuki(dot)kadomoto(at)proceranetworks(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Tatsuki Kadomoto <tatsuki(dot)kadomoto(at)proceranetworks(dot)com> |
| Cc: | Kevin Grittner <kgrittn(at)gmail(dot)com>, John R Pierce <pierce(at)hogranch(dot)com>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed |
| Date: | 2016-08-26 00:09:43 |
| Message-ID: | u537pwebckiob3m5oyag7wo0.1472170180957@email.android.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(dot)kadomoto(at)proceranetworks(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ahsan Ali | 2016-08-26 00:10:02 | Re: LOG: could not fork new process for connection: Cannot allocate memory |
| Previous Message | Michael Paquier | 2016-08-26 00:05:50 | Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed |