I'm currently dealing with a tricky issue where Temporal connects to a PostgreSQL database. The setup uses a hardcoded hostname pattern for the primary instance such as `host: ..`. This works fine initially, but it breaks when a PostgreSQL replica is promoted to primary during a failover. The hostname becomes outdated since the primary pod name changes with the switch. I'm looking for a way to configure Temporal so it can automatically connect to the new primary PostgreSQL instance without manual intervention after a failover. Any ideas?
2 Answers
Yeah, I ran into the same issue! When I set it up through Helm, I made sure to update the values in the installation configuration. Definitely look into that README; it should guide you on keeping your connection dynamic rather than static.
Have you tried checking how you've installed Temporal? If it's via Helm, there’s a README guide on their GitHub that might help you set it up properly with PostgreSQL. It could include steps on how to manage dynamic connections to the primary instance, which sounds like what you need.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically