Managing multiple databases in Rails 6

In the upcoming Rails 6 (currently in RC1), you will be able to easily change which database server you are connecting to, so you can support followers (aka read replicas) and splitting your database into dedicated components. In this post, Lukas explains how to configure automatic queries against read replicas in Rails 6.
Read Lukas’s post → 

More technical details on pg_auto_failover

In this post, Dimitri Fontaine, one of the developers of pg_auto_failover, provides more detail on how pg_auto_failover works. When designing pg_auto_failover, our goal was to provide an easy-to-set-up business continuity solution for Postgres that implements fault tolerance of any node in the system.
Read the deets on pg_auto_failover → 

What’s happening with Citus and Microsoft Azure?

Hyperscale (Citus) is now available in preview on Azure Database for PostgreSQL. Want to stay in the loop? We’ve made it easy for you. Just sign up to the Citus on Azure interest list.
Sign up on the Citus on Azure interest list → 

ICYMI: A health check playbook for your Postgres database

Our Citus team has a lot of experience running and managing Postgres databases. In this post, you’ll find our breakdown of what your regular Postgres health check should look like. Think about running this on a monthly basis to be able to make small tweaks and adjustments and avoid the drastic changes. A santé!
Health check playbook → 

Operationalizing your PostgreSQL database health checks using SQL Notebooks

In Craig’s blog post, “A health check playbook for your Postgres database” he emphasizes the need for periodic checks for your Postgres databases to ensure it’s healthy and performing well. Most Postgres users might bookmark or save such articles for easy access when needed. The trouble with this approach is, you end up with many saved archives, and searching through them when you need it is time consuming and less productive. Another way: create SQL Notebooks in Azure Data Studio.
More on SQL Notebooks →