Hi everyone, ran into a weird issue in production. We run supertokens in an ecs cluster and have two replicas of it. Our server was not responding for few minutes upon investigating this SQL query was stuck in postgres and causing everything to slow down.

SELECT * FROM supertokens.jwt_signing_keys ORDER BY created_at DESC FOR UPDATE

We use static signing keys and run version 5 of supertokens. Did anyone else also face this issue ever? For the time being I have killed the query manually, is there any way I can avoid this in future.