Re: Data Corruption Errors

From: Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Data Corruption Errors
Date: 2018-09-27 13:13:55
Message-ID: 78ea6e8f-a55b-5724-c86e-723a4e7b9e19@matrix.gatewaynet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On 27/9/18 3:39 μ.μ., Ferrell, Denise SDC wrote:
> Using Linux/PostgreSQL 9.5 & setup on a VM.
>
> I'm receiving the following errors during an insert using a function but this does not happen every time. When this does occur the database/system is unavailable until the processes are killed or the service is restarted.
>
> "LOG: server process (PID xxxxx) was terminated by signal 9: Killed
> DETAIL: Failed process was running
> select insert_data ($1, $2,....)
> WARNING: terminating connection because of crash of another server process
> DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
> HINT: In a moment you should be able to reconnect ....
> LOG: connection received
> FATAL: the database system is in recovery mode"

Did your DB eventually recover? Have you ruled reasons like OOM, non-optimal vm.swapiness , etc ?

>
> The last 2 lines are repeated and logging is not available.
>
> How can I determine data/table/shared memory corruption?
>
> Thank you in advance for your responses.
>
> D. Ferrell

--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Kevin Grittner 2018-09-27 13:24:31 Re: Data Corruption Errors
Previous Message Ferrell, Denise SDC 2018-09-27 12:39:33 Data Corruption Errors