PostgreSQL Logical Replication Guide

0:00 - Content of this video
0:22 - What is Logical Replication in Postgres?
5:54 - Step by step Logical Replication setup
Setting up the servers for Logical Replication
10:38 - Selective Copy of the Data
13:53 - Create the Publication
14:41 - Create the Subscription
17:43 - Postgres Limitations of Logical Replication
20:06 - Monitoring Logical Replication
23:16 - Best use-cases

🐘 Want to find out MORE about Scaling PostgreSQL?
Use the link below to get 60% OFF on the Entire Course.

[scottspitlerII]

God you made such a good video! Seriously no one has put anything as good as this up!

[arreyettabawakaugustinebes]

You are a lifesaver! 🙌 God bless you! I’ve been working on a project for about a month that required logical replication. After trying several methods and reading various documents, I was really unsure about what to do since it kept failing. Today, I decided to dive back into research and accidentally stumbled upon your video. After watching it, I realized where I went wrong and immediately got back to it. I finally succeeded! 🎉 Thank you so much! I’m at a loss for words! ❤

[joobis.b]

i found this channel today and watched 2 of them and I'm really impressed, thankyou for the effort!

[ashutoshsharma]

Exactly the thing I was looking for, bullseye, Loved it!!

[habbex]

Thank you for the great explanation on the topic of logical replication, keep up the good work!

[agoodmuffin]

Very good content.
The video is well structured,
illustrations are straightforward & pleasant to look at,
and you are speaking very clearly. Keep it up
+1

[kalyaninagul]

Thank you so much for this video. Very detailed and with good examples.

[artemiypyatakov]

You are so good in a teaching. Please keep going.

[DanutSoare]

Hi. Very good presentation of logical replication! One thing I want to mention is that schema is not the same as the database. In this case, the schema used was Public and the database name was Pub.

[gabrielosorioo]

This is amazing content, thank you very much, won another subscriber

[anton-r]

so match senk you, great explanation

for docker users that using psql 11 wal lvl ->

command:
- "postgres"
- "-c"
- "wal_level=logical"

[clouddeep]

Very nice and clear guide, thank you.

[veerareddy]

Very good explanation. If possible please provide upgrade using logical replication. How to ignore Deletes or update in logical replication.

[utkarshshukla]

Nice explanation sir, can you please make video on BDR (Bi directional replication)

[AuthorReviews]

Thanks for the video. But I'm facing some issues. First of all I'm running both servers in Docker containers. I use Dbeaver to connect to database and manage it. When i create Database everything works fine. Once I change postgresql.conf file and restart postgres in container I can't connect to it using Dbeaver, although I can manage database in docker container. Another issue is with dumping and restoring at the same time - never works like in your video. I don;t know what am I doing wrong. Coudn't find any solution.

[martindominikus]

Great video! By the way, is there a way to store the replication log? I need to know the timestamp when the DML operation occurs, or if I can write a code that pull the timestamp and store it back to the table, is there a way to see these logs stream?

[varunverma]

I have a doubt can logical replication be the solution to long running queries getting cancelled due to replication lag, I understand more replication lag means too much updates on the master/publisher side and subscriber/replica is taking time to catchup, But is there anyway in which logical replication can help in this case over physical replication
BTW thanks for the great content you are providing!!

[WaseemNazirMir]

i have seen that there are changes in hba.conf as well, but you did not did that.. Also is it simialr for managed DB as well?

[utkarshshukla]

sir please make video on BDR replicational also

[MarkJones]

DDL statements seem to flow thru on PGv14. At least our replica has changes that were made to the schema from our prod db.