3 ms·
The postgres documentation for logical replication suggests using "pg_dump --schema-only" as a starting point. I am sure the pg_easy_replicate tool brings some
by somat 3y ago
The postgres documentation for logical replication suggests using "pg_dump --schema-only" as a starting point.
I am sure the pg_easy_replicate tool brings something to the table(probably replication lifecycle management) but reading the docs, the bare postgres replication looks just as easy if not easier than the easy replicate tool. I am going to try it on my toy db and see how it goes.
https://www.postgresql.org/docs/13/logical-replication-restrictions.html https://www.postgresql.org/docs/13/logical-replication-restr...
- nijave 3y agoThis looks like a script that basically just runs all the necessary SQL for you. It looks pretty similar to an internal Python tool I came up with to do the same thing (basically just scripting out setting up logical rep and waiting for it to catch up, then executing switchover commands)
- shayonj 3y agoThats right! Its mostly a CLI orchestration tool (mentioned in the readme), with some logging, stats and safety checks so that user/engineer can be mostly hands off during the process. Perhaps, even automate the entire process by wiring up different pg_easy_replicate commands together. We do that with Tines, where we can be fully hands off (zero touch ops) and are able to kick off upgrade with switchover for tens of DBs (one at a time for now :D).