migrations could trigger 'out of shared memory' error on postgres

From andrewklau on discord.

FATA[0019] apply failed: [postgres-error] postgres query error ($.args[112].args)
File: ''
[53200] FatalError: out of shared memory
Hint: You might need to increase max_locks_per_transaction. 

Workarounds:

1. https://github.com/hasura/graphql-engine/issues/1325#issuecomment-452216310
2. https://github.com/hasura/graphql-engine/issues/1325#issuecomment-453825062

[elgordino]

I hit this with my docker postgres instance when performing many ALTER TABLE commands. In my use case I don’t see it as an Hasura issue, I want all these actions performed in a single transaction. Modifying the docker-compose to set the max_locks_per_transaction worked

    image: postgres
    restart: always
    ports:
    - "5432:5432"
    volumes:
    - db_data:/var/lib/postgresql/data
    command: postgres -c max_locks_per_transaction=2000

[howientc]

Just starting running into this on Azure Postgres. Don’t see a way to set the max_locks_per_transaction on that.

Squashing worries me - what happens when this occurs again? If I squash then, how does it know which migrations to apply?