How it works…

This entire recipe is essentially optional, but makes a good checklist of elements we may wish to consider when cleaning up after such a major upgrade.

The first steps are optional because we may find that we need pglogical for transmitting table data to other parts of the cluster. So long as it's installed and listed in postgresql.conf, we could use it either for future upgrade needs, or managing any number of full or partial logical replicas. Some enterprises may dictate that any unused extensions should be uninstalled, and if that is the case, we may as well do that first.

Next, we need to enable any software that manages the cluster in ways that we may have temporarily disabled during the transition. We wouldn't want an ...

Get PostgreSQL 12 High Availability Cookbook now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.