Hello,

I'm experiencing some issues with my services on Railway and need detailed help to resolve them. I've identified two critical issues in the logs and would like to request assistance from a technician to guide me, or, if possible, perform the procedures with me.

1. PostgreSQL "Collation Mismatch"

The first problem is a recurring warning in my PostgreSQL service logs: "WARNING: database 'railway' has a collation version mismatch".

I understand that the safest solution is to:

1. Create a complete backup of my current database.
2. Delete the existing database service on Railway.
3. Create a new PostgreSQL service so it is provisioned with the correct collation version.
4. Import the data from the backup into the new database.

I would like to know if it's possible for a technician to help me execute these steps. I need precise guidance to ensure I don't lose any data during this migration process.

2. Redis "Memory Overcommit" Warning

The second issue is a critical warning in my Redis service logs: "WARNING Memory overcommit must be enabled!".

I understand that this configuration is crucial for Redis to perform background operations, like data persistence and replication, without failures. However, I don't have direct access to the operating system environment to enable this setting using the sysctl vm.overcommit_memory=1 command.

Could you please advise me on the best way to resolve this within the Railway environment? Or, if necessary, perform the change for me?

I appreciate your attention and kindly ask for assistance from a specialist. I am available to schedule a conversation or follow your instructions.