Since switching to cimg/postgres:11.13 (from circleci/postgres:11-alpine-ram) we've seen intermittent errors like:
django.db.utils.OperationalError: out of shared memory
HINT: You might need to increase max_locks_per_transaction.
While I'm not sure if the issue is actually related to the change of image, I can't see in the docs any means to configure the Postgres instance. As this setting is one which requires a postgres restart, ideally it's something I'd configure before the container starts.
Is this a case of creating a custom image, or is there a way to overlay Postgres' configuration via CI config?
Since switching to cimg/postgres:11.13 (from circleci/postgres:11-alpine-ram) we've seen intermittent errors like:
While I'm not sure if the issue is actually related to the change of image, I can't see in the docs any means to configure the Postgres instance. As this setting is one which requires a postgres restart, ideally it's something I'd configure before the container starts.
Is this a case of creating a custom image, or is there a way to overlay Postgres' configuration via CI config?