Logical Replication hung: logical_decoding_work_mem over utilised

Поиск
Список
Период
Сортировка
От Nikhil Shetty
Тема Logical Replication hung: logical_decoding_work_mem over utilised
Дата
Msg-id CAFpL5VwaQ0fNaBV1z76pDX726bkruccxaKsWY2Wccs5tQnsCnA@mail.gmail.com
обсуждение исходный текст
Список pgsql-admin
Hi Team,

I faced a scenario where after a heavy update query (touching ~100k records) the logical replication was hung.

After enabling debug logging, we found it was spilling to disk and increased logical_decoding_work_mem from 64MB to 4GB. Replication started working after that

I am trying to understand why the replication was just hung ? Also, How do we decide for an optimal configuration of logical_decoding_work_mem.?

Even if it reaches 64MB, it should be able to spill to disk and continue, may be not at the same speed but slowly

Note: There were no subtransactions involved, it was a simple update query touching a lot of records.

Thanks,
Nikhil

В списке pgsql-admin по дате отправления:

Предыдущее
От: Rajesh Kumar
Дата:
Сообщение: Re: Autovacuum not running properly
Следующее
От: richard coleman
Дата:
Сообщение: Why isn't there a IF NOT EXISTS clause on constraint creation?