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! ❤
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
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.
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.
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!!
Ok, and what if subscriber has outage - not connected some time...( Hours,days...) And then connected back, how will be then sql data replicated in what order ?
I believe you will need to reinitialize the stream with the last processed LSN (log sequence number) which can be stored in a shared, persistent state. If you have more than one consumer, more logic and data will be required.
I got an error could not connect to the publisher: connection to server at "ip host", port 5432 failed: fe_sendauth: no password supplied , How should I deal with it, help me, please.
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?
I will like to talk to you, I really like your lectures on Postgres. Please send me your email address, I will like to talk about my interest of becoming DBA
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! ❤
Thank you so much for your comment. This means a lot to me. ❤️
God you made such a good video! Seriously no one has put anything as good as this up!
That is true! Theo best tutoriale what I've ever seen. Thank you.
i found this channel today and watched 2 of them and I'm really impressed, thankyou for the effort!
Thank you for the great explanation on the topic of logical replication, keep up the good work!
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
Thank you so much for this video. Very detailed and with good examples.
You are so good in a teaching. Please keep going.
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.
so match senk you , great explanation
for docker users that using psql 11 wal lvl ->
command:
- "postgres"
- "-c"
- "wal_level=logical"
Is it possible to create a video for Bidirectional Logical Replication in PostgreSQL 16
Very good explanation. If possible please provide upgrade using logical replication. How to ignore Deletes or update in logical replication.
This is amazing content, thank you very much, won another subscriber
pg_ctl: could not open PID file "/tmp/publication_db/postmaster.pid": Permission denied
i changing owner to postgres already but still have errors
Nice explanation sir , can you please make video on BDR (Bi directional replication)
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.
Very nice and clear guide, thank you.
Can this logical replication use for other databases like mongodb?
DDL statements seem to flow thru on PGv14. At least our replica has changes that were made to the schema from our prod db.
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!!
Hi everything is good but iam not able to get replicated the tables which are generated from11 to 20 please provide answer for this error.
Good content, thank you very much
Thank you very much. great video
Great explanation!
Ok, and what if subscriber has outage - not connected some time...( Hours,days...) And then connected back, how will be then sql data replicated in what order ?
I believe you will need to reinitialize the stream with the last processed LSN (log sequence number) which can be stored in a shared, persistent state.
If you have more than one consumer, more logic and data will be required.
I got an error could not connect to the publisher: connection to server at "ip host", port 5432 failed: fe_sendauth: no password supplied , How should I deal with it, help me, please.
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?
sir please make video on BDR replicational also
Great content
I will like to talk to you, I really like your lectures on Postgres. Please send me your email address, I will like to talk about my interest of becoming DBA