From: | Japin Li <japinli(at)hotmail(dot)com> |
---|---|
To: | Aleksander Alekseev <aleksander(at)timescale(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-08 02:20:21 |
Message-ID: | MEYP282MB16696310F20D7E8B6C24A854B6379@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 07 Jun 2021 at 19:25, Aleksander Alekseev <aleksander(at)timescale(dot)com> wrote:
> 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.
>
Thanks for your explanation.
> 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
Sorry for my poor reading of the documentation.
--
Regrads,
Japin Li.
ChengDu WenWu Information Technology Co.,Ltd.
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuro Yamada | 2021-06-08 02:33:16 | Re: Duplicate history file? |
Previous Message | Julien Rouhaud | 2021-06-08 01:51:34 | Re: SQL-standard function body |