From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Rajan Pandey <rajanpandey2508(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Possible to exclude a database from loading a shared_preload_libraries module? |
Date: | 2024-04-19 14:10:21 |
Message-ID: | 2136292.1713535821@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Rajan Pandey <rajanpandey2508(at)gmail(dot)com> writes:
> Hi, I have a use case where I want a particular database to not load a few
> modules in shared_preload_libraries.
> I was wondering if there's any way to tweak the codebase to achieve this.
No. It's not even theoretically possible, because the whole point of
shared_preload_libraries is that the module gets loaded at postmaster
start.
Depending on what the module does, it might work to load it
per-session with session_preload_libraries, which you could attach
to the specific database(s) where you want it to be effective.
> Otherwise, can I block the modules' hooks/bgw from performing actions on my
> particular database?
That would be a feature for the individual module to implement.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Euler Taveira | 2024-04-19 14:12:54 | Re: Idea Feedback: psql \h misses -> Offers Links? |
Previous Message | Heikki Linnakangas | 2024-04-19 13:55:55 | Re: Direct SSL connection with ALPN and HBA rules |