PostgreSQL 12 High Availability Cookbook - Third Edition

There's more...

Remember in step 3 how we defined the replication set to only forward INSERT and UPDATE statements? The primary reason to do something like this is that we're sending data to some kind of archival system. Since these types of databases tend to accumulate data for months or even years, they're also commonly partitioned. The pglogical extension is perfectly compatible with this approach, but there is one caveat.

Before PostgreSQL 10 introduced native partitioning, partitions were usually managed via a trigger and a complicated series of constraints to distribute data based on inheritance rules. Reporting or other data accumulation systems that use this approach rely on this trigger to ensure data is deposited in the correct ...