| From: | Sathish Reddy <sathishreddy(dot)postgresql(at)gmail(dot)com> |
|---|---|
| To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Debizium configure from Kafka side |
| Date: | 2024-07-11 13:13:35 |
| Message-ID: | CA+M9Y+D2ndxkAjEG9bQ1hZcYjvLF7-qSkQAwEjLK3aV12+gP3w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
How can we minimize replication lag between pgsql db and Kafka whenever we
have more workload at dbside
Could you please let me know what are the important parameters that need to
be focused to manage replication lag
Does debeziium use work_mem value or logical decoding work mem param value
with which we can manage tables mapping and buffered data to be replicated
to target to Kafka topics based on mapping scenario
What are important debeziium and Kafka side params that need to be fine
optimised to manage replication lag even on high db workload
Please share me in detail.
Thanks
Sathish Reddy
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2024-07-11 16:03:22 | Better way to find long-running queries? |
| Previous Message | Ron Johnson | 2024-07-11 12:39:18 | Re: indexes on partitioned tables |