Current state:

Working with 3scale 2.14 and AWS Aurora RDS Postgres v13.x, without superuser Zync was restarted. But when DBA grants superuser to database user zync, this problem is resolved. When it removes the user's access from the zync database and if the zync pods restart, we get back to bellow error.

• zync service worked without these problems and without superuser in versions prior to 2.14.

Zync and Zync Queue pods unable to start after a pod restart due to:
D, 2024-05-22T20:43:52.885574 #1 DEBUG – : (1.2ms) CREATE TABLE "schema_migrations" ("version" character varying NOT NULL PRIMARY KEY)
I, 2024-05-22T20:43:52.885741 #1 INFO – : Completed 500 Internal Server Error in 9ms (ActiveRecord: 3.9ms | Allocations: 3274)
D, 2024-05-22T20:43:52.885925 #1 DEBUG – [Bugsnag]: Not notifying due to an invalid api_key
F, 2024-05-22T20:43:52.886211 #1 FATAL – :
ActiveRecord::StatementInvalid (PG::InvalidSchemaName: ERROR: no schema has been selected to create in
LINE 1: CREATE TABLE "schema_migrations" ("version" character varyin...
Desired state:

   An alternative to running the zync service on RDS Postgres 13.x without the super user, perhaps documentation with details of which permissions are mandatory in this version 2.14 as opposed to the previous ones.