Re: Logical replication prefetch
От | Amit Kapila |
---|---|
Тема | Re: Logical replication prefetch |
Дата | |
Msg-id | CAA4eK1LkMjFJTM5ZCtcgDSyMRKwNUvGQVXTWjAyPO-7rYM=MyA@mail.gmail.com обсуждение исходный текст |
Ответ на | Logical replication prefetch (Konstantin Knizhnik <knizhnik@garret.ru>) |
Ответы |
Re: Logical replication prefetch
|
Список | pgsql-hackers |
On Tue, Jul 8, 2025 at 12:06 PM Konstantin Knizhnik <knizhnik@garret.ru> wrote: > > There is well known Postgres problem that logical replication subscriber > can not caught-up with publisher just because LR changes are applied by > single worker and at publisher changes are made by > multiple concurrent backends. > BTW, do you know how users deal with this lag? For example, one can imagine creating multiple pub-sub pairs for different sets of tables so that the workload on the subscriber could also be shared by multiple apply workers. I can also think of splitting the workload among multiple pub-sub pairs by using row filters. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: