| From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
|---|---|
| To: | Japin Li <japinli(at)hotmail(dot)com> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Confused about extension and shared_preload_libraries |
| Date: | 2021-06-07 11:25:31 |
| Message-ID: | CAJ7c6TMOScOH+ejtNjRTg5GrgY8LyfJAJwjm4SwOgcErp3iDNg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | houzj.fnst@fujitsu.com | 2021-06-07 11:38:40 | RE: Skip partition tuple routing with constant partition key |
| Previous Message | Japin Li | 2021-06-07 11:18:34 | Confused about extension and shared_preload_libraries |