Re: "out of relcache_callback_list slots" after multiple calls to pg_logical_slot_get_binary_changes

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: "out of relcache_callback_list slots" after multiple calls to pg_logical_slot_get_binary_changes
Дата
Msg-id 3569225.1676907043@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: "out of relcache_callback_list slots" after multiple calls to pg_logical_slot_get_binary_changes  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Ответы RE: "out of relcache_callback_list slots" after multiple calls to pg_logical_slot_get_binary_changes  ("shiy.fnst@fujitsu.com" <shiy.fnst@fujitsu.com>)
Список pgsql-hackers
Kyotaro Horiguchi <horikyota.ntt@gmail.com> writes:
> I'm pretty sure that everytime an output plugin is initialized on a
> process, it installs the same set of syscache/relcache callbacks each
> time.  Do you think we could simply stop duplicate registration of
> those callbacks by using a static boolean?  It would be far simpler.

Yeah, I think that's the way it's done elsewhere.  Removing and
re-registering your callback seems expensive, and it also destroys
any reasoning that anyone might have made about the order in which
different callbacks will get called.  (Admittedly, that's probably not
important for invalidation callbacks, but it does matter for e.g.
process exit callbacks.)

            regards, tom lane



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

Предыдущее
От: Aleksander Alekseev
Дата:
Сообщение: Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15)
Следующее
От: Tom Lane
Дата:
Сообщение: Re: ExecRTCheckPerms() and many prunable partitions (checkAsUser)