RE: "out of relcache_callback_list slots" after multiple calls to pg_logical_slot_get_binary_changes - Mailing list pgsql-hackers

From shiy.fnst@fujitsu.com
Subject RE: "out of relcache_callback_list slots" after multiple calls to pg_logical_slot_get_binary_changes
Date
Msg-id OSZPR01MB631047D0B585B2EEC2A8380EFDA59@OSZPR01MB6310.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: "out of relcache_callback_list slots" after multiple calls to pg_logical_slot_get_binary_changes  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: "out of relcache_callback_list slots" after multiple calls to pg_logical_slot_get_binary_changes
List pgsql-hackers
On Mon, Feb 20, 2023 11:31 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 
> 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.)
> 

Thanks for your reply. I agree that's expensive. Attach a new patch which adds a
static boolean to avoid duplicate registration.

Regards,
Shi Yu

Attachment

pgsql-hackers by date:

Previous
From: Nazir Bilal Yavuz
Date:
Subject: Re: meson logs environment
Next
From: Heikki Linnakangas
Date:
Subject: Re: ResourceOwner refactoring