Today, when trying to build and run my application I discover that Postgres suddenly terminates unexpectedly during the initialization of the application.

When doing further investigation I can see that latest Postgres image now is version 11. (I hadn't specified to use specific version in Dockerfile).

My application does a bunch of initialization tasks on start, and Postgres terminates during one of these.

Going back to version 10.5 solves the issue for me, but there is certainly an issue either with Postgres it self, or configuration issue with the default config in pg11 for the Docker image.

Here is my log output:

api_1 | Exception: SQLSTATE[HY000]: General error: 7 server closed the connection unexpectedly
api_1 | This probably means the server terminated abnormally
api_1 | before or while processing the request.
api_1 | Exception 'PDOException' with message 'SQLSTATE[HY000]: General error: 7 no connection to the server'
db_1 | 2018-10-30 09:48:50.610 UTC [1] LOG: server process (PID 71) was terminated by signal 11: Segmentation fault
db_1 | 2018-10-30 09:48:50.610 UTC [1] DETAIL: Failed process was running: DELETE FROM "dashboard_layouts" WHERE "position"=$1
db_1 | 2018-10-30 09:48:50.610 UTC [1] LOG: terminating any other active server processes
db_1 | 2018-10-30 09:48:50.610 UTC [67] WARNING: terminating connection because of crash of another server process
db_1 | 2018-10-30 09:48:50.610 UTC [67] 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.
db_1 | 2018-10-30 09:48:50.610 UTC [67] HINT: In a moment you should be able to reconnect to the database and repeat your command.
db_1 | 2018-10-30 09:48:50.613 UTC [1] LOG: all server processes terminated; reinitializing
db_1 | 2018-10-30 09:48:50.627 UTC [72] LOG: database system was interrupted; last known up at 2018-10-30 09:48:46 UTC
db_1 | 2018-10-30 09:48:50.944 UTC [72] LOG: database system was not properly shut down; automatic recovery in progress
db_1 | 2018-10-30 09:48:50.950 UTC [72] LOG: redo starts at 0/1654800
db_1 | 2018-10-30 09:48:50.971 UTC [72] LOG: invalid record length at 0/17C72F8: wanted 24, got 0
db_1 | 2018-10-30 09:48:50.971 UTC [72] LOG: redo done at 0/17C72D0
db_1 | 2018-10-30 09:48:50.971 UTC [72] LOG: last completed transaction was at log time 2018-10-30 09:48:50.600994+00
db_1 | 2018-10-30 09:48:51.054 UTC [1] LOG: database system is ready to accept connections