Re: Proposal - Allow extensions to set a Plan Identifier - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Proposal - Allow extensions to set a Plan Identifier
Date
Msg-id Z-CewTjALX80nbkL@paquier.xyz
Whole thread Raw
In response to Re: Proposal - Allow extensions to set a Plan Identifier  (Andrei Lepikhov <lepihov@gmail.com>)
List pgsql-hackers
On Sun, Mar 23, 2025 at 04:30:04PM +0100, Andrei Lepikhov wrote:
> So, it may be not an issue in a cloud provider predefined installations, but
> a headache for custom configurations.

Sure, I mean, but it's not really related to the issue discussed on
this thread, so..

It sounds like we could improve the documentation about the GUCs that
hold a list of library names and load them in the order specified, so
as we could point somewhere rather that just saying "don't do that".
Another thing is extensions that have the idea of not tracking a hook
previously registered, and missing to call it.  Another one is that
the previous hook can be called before a module's look, or after it.
Depending on how an out-of-core extension is maintained, there are a
lot of things that can be done.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Fwd: [BUG]: the walsender does not update its IO statistics until it exits
Next
From: Noah Misch
Date:
Subject: Re: AIO v2.5