Oh that solution is a garbage fire. We hit the 4tb storage limit that they didn't tell us about on it when the documentation said 16tb. They told us we were on

Oh that solution is a garbage fire. We hit the 4tb storage limit that they didn't tell us about on it when the documentation said 16tb. They told us we were on the older storage tier and that we needed to rebuild a huge analytics database on our time because they couldn't migrate us to a backend storage tier. So we had a database server that was in read only mode until we could migrate off of it. Then we had random restarts and outages with their proxy that handles all of the connections. Which is why you actually need the username@db-name, because without the @db-name it doesn't know where to route you, because the postgres connection string is actually just mapping to one IP that they manage for multiple databases! Fun trick is you can make your url anything that maps to the IP they use for their proxy and it'll take you to whatever the @db-name is in your connection string. Their solution to the random connections dropping for minutes at a time was to "implement retry logic" on our applications. Our solution was to migrate away from it.