Avoid unnecessary ReplicationSlotControl lwlock acquistion

Поиск
Список
Период
Сортировка
От Masahiko Sawada
Тема Avoid unnecessary ReplicationSlotControl lwlock acquistion
Дата
Msg-id CA+fd4k4v6t-8VYsz-U3XSCOjPDhDg67eNk33+ZAf53n9bmNo=w@mail.gmail.com
обсуждение исходный текст
Ответы Re: Avoid unnecessary ReplicationSlotControl lwlock acquistion  (Andres Freund <andres@anarazel.de>)
Список pgsql-hackers
Дерево обсуждения 
Hi all,

While testing with DTrace, I realized we acquire
ReplicationSlotControl lwlock at some places even when
max_replication_slots is set to 0. For instance, we call
ReplicationSlotCleanup() within PostgresMian() when an error happens
and acquire ReplicationSlotControl lwlock.

The attached patch fixes some functions so that we quickly return if
max_replication_slots is set to 0.

Regards,

-- 
Masahiko Sawada            http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Вложения

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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: Problems with the FSM, heap fillfactor, and temporal locality
Следующее
От: Fujii Masao
Дата:
Сообщение: Re: Creating a function for exposing memory usage of backend process