This seems to have been the issue. Thank you for the responses. ________________________________________ From: Kevin Grittner <kgrittn@xxxxxxxxx> Sent: Thursday, September 27, 2018 9:24 AM To: Ferrell, Denise SDC Cc: pgsql-admin@xxxxxxxxxxxxxx Subject: Re: Data Corruption Errors On Thu, Sep 27, 2018 at 7:40 AM Ferrell, Denise SDC <denise.ferrell@xxxxxxxxxxxxx> wrote: > Using Linux/PostgreSQL 9.5 & setup on a VM. Please always show the entire version number -- it can matter a lot. One way to see it is to run `select version();` on a database connection. From the shell you can run one of the executables with the --version option, which will show the version and do nothing else. If you are running in a VM, please say which product, and show the exact version of that. > 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" > > The last 2 lines are repeated and logging is not available. > > How can I determine data/table/shared memory corruption? You have not shown any evidence of corruption. What happened was that some database service process was killed with SIGKILL (kill -9). Never do that. It may have been done by the Out of Memory Killer process. You should disable that by setting vm.overcommit_memory=2 and vm.overcommit_ratio=80 *or maybe as high as 90). When a database service process is killed with SIGKILL the service cannot continue without *RISK* of corruption, so it does a crash and restart. These messages: FATAL: the database system is in recovery mode Just mean that an attempt was made to the database while the recovery was in progress, so the connection attempt was rejected. Just ignore those messages. Just wait for the service to restart. -- Kevin Grittner VMware vCenter Server https://www.vmware.com/
