vacuum issues

gistfile1.txt

Jun 21 20:54:52 vapipeline01 kernel: [2239310.896998] Out of memory: Kill process 1056 (pipelinedb) score 506 or sacrifice child
Jun 21 20:54:52 vapipeline01 kernel: [2239310.903418] Killed process 1056 (pipelinedb) total-vm:12751636kB, anon-rss:8306604kB, file-rss:128kB
Jun 21 20:54:52 vapipeline01 pipeline[15284]: [342-1] LOG:  autovacuum launcher process (PID 1056) was terminated by signal 9: Killed
Jun 21 20:54:52 vapipeline01 pipeline[15284]: [343-1] LOG:  terminating any other active server processes
Jun 21 20:54:52 vapipeline01 pipeline[1060]: [295-1] WARNING:  terminating connection because of crash of another server process
Jun 21 20:54:52 vapipeline01 pipeline[1191]: [294-1] WARNING:  terminating connection because of crash of another server process
Jun 21 20:54:52 vapipeline01 pipeline[1059]: [310-1] WARNING:  terminating connection because of crash of another server process
Jun 21 20:54:52 vapipeline01 pipeline[1162]: [294-1] WARNING:  terminating connection because of crash of another server process
Jun 21 20:54:52 vapipeline01 pipeline[1219]: [294-1] WARNING:  terminating connection because of crash of another server process
Jun 21 20:54:52 vapipeline01 pipeline[1203]: [294-1] WARNING:  terminating connection because of crash of another server process
Jun 21 20:54:52 vapipeline01 pipeline[12664]: [1933-1] admin01WARNING:  autovacuum worker started without a worker entry
Jun 21 20:54:52 vapipeline01 pipeline[1162]: [294-2] 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.
Jun 21 20:54:52 vapipeline01 pipeline[1162]: [294-3] HINT:  In a moment you should be able to reconnect to the database and repeat your command.
Jun 21 20:54:52 vapipeline01 pipeline[1191]: [294-2] 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.
Jun 21 20:54:52 vapipeline01 pipeline[1191]: [294-3] HINT:  In a moment you should be able to reconnect to the database and repeat your command.
Jun 21 20:54:52 vapipeline01 pipeline[1059]: [310-2] 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.
Jun 21 20:54:52 vapipeline01 pipeline[1059]: [310-3] HINT:  In a moment you should be able to reconnect to the database and repeat your command.
Jun 21 20:54:52 vapipeline01 pipeline[1060]: [295-2] 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.
Jun 21 20:54:52 vapipeline01 pipeline[1060]: [295-3] HINT:  In a moment you should be able to reconnect to the database and repeat your command.
Jun 21 20:54:52 vapipeline01 pipeline[1219]: [294-2] 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.
Jun 21 20:54:52 vapipeline01 pipeline[1219]: [294-3] HINT:  In a moment you should be able to reconnect to the database and repeat your command.
Jun 21 20:54:52 vapipeline01 pipeline[1203]: [294-2] 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.
Jun 21 20:54:52 vapipeline01 pipeline[1203]: [294-3] HINT:  In a moment you should be able to reconnect to the database and repeat your command.