Re: Confused about extension and shared_preload_libraries - Mailing list pgsql-hackers

From Aleksander Alekseev
Subject Re: Confused about extension and shared_preload_libraries
Date
Msg-id CAJ7c6TMOScOH+ejtNjRTg5GrgY8LyfJAJwjm4SwOgcErp3iDNg@mail.gmail.com
Whole thread Raw
In response to Confused about extension and shared_preload_libraries  (Japin Li <japinli@hotmail.com>)
Responses Re: Confused about extension and shared_preload_libraries  (Japin Li <japinli@hotmail.com>)
List pgsql-hackers
Hi Japin,

> When we write a extension using C language, we often add the dynamic library
> into shared_preload_libraries, however, I found that the bloom, btree_gist and
> btree_gin do not follow this rule.  I'm a bit confused with this, could anybody
> explain it for me?

In the general case, you don't need to modify shared_preload_libraries to use an extension, regardless of the language in which it's implemented. That's it.

Some extensions may however require this. See the description of the GUC [1].

[1]: https://www.postgresql.org/docs/13/runtime-config-client.html#GUC-SHARED-PRELOAD-LIBRARIES

--
Best regards,
Aleksander Alekseev

pgsql-hackers by date:

Previous
From: Japin Li
Date:
Subject: Confused about extension and shared_preload_libraries
Next
From: "houzj.fnst@fujitsu.com"
Date:
Subject: RE: Skip partition tuple routing with constant partition key