Weird DB connection error

[tabeckers]

Situation
Upon migrating to a new database with EXACTLY the same data and schema (pg_dump => pg_restore), some weird bugs appeared. The connection strings were replaced and the login was valid, as the logs of our new database showed. The errors that were shown in the logs dictated parsing errors:

Error parsing column 4 (push_notification_platform=9107273536666885396-4160809626774872611-1 - String)

This column consists of either 'fcm' or 'apns', so clearly something went wrong with the column parsing process.

Fix checks

• When the API was run on a localhost, none of these problems appeared.
• When the API connection string was changed back to point to the old database, none of these problems appeared.
• When the API connection string once again pointed to the new database (after pointing to the old database), none of these problems appeared.

Conclusion
This behaviour is really weird and has no explanation as of now. The service works as it should right now, but the cause of the mentioned problems remains a mystery.