Date: 30th May 2017

Up-time is very critical for any database and running a replica database will help you perform a fail-over (manual/automated) when primary server goes down. This also helps avoiding downtime because of unforeseen issues. But more often you come across scenarios where a planned activity leads to some downtime. Most commonly, while patching the database software. A lot of people think that applying a patch would require bringing down the database services and this will impact the availability. This is one single largest reason for many people to not promptly apply patches to their database. Let us understand how we can overcome this.

In this hangout, you will learn about:

• Some of the reasons why you should consider applying a patch promptly
• Best practices and procedure that can help you achieve ‘Near Zero Downtime Patching for Postgres’

Our previous hangout covered:

• How to run highly available PostgreSQL in cloud