Re: Regarding shared_preload_libraries (postgresql.conf file) - Mailing list pgsql-hackers

From David Fetter
Subject Re: Regarding shared_preload_libraries (postgresql.conf file)
Date
Msg-id 20180705153250.GD22932@fetter.org
Whole thread Raw
In response to Regarding shared_preload_libraries (postgresql.conf file)  (Abi KR <abi.kr.2016@gmail.com>)
List pgsql-hackers
On Thu, Jul 05, 2018 at 06:46:26PM +0530, Abi KR wrote:
> hello everyone,
>      We wanted to make use of embedded key-value store(BadgerDB -
> implemented in golang) to save the data related to our extension.
> 
> 
> The problem is,
>     when we load our extension using shared_preload_libraries, we could
> able to open badgerdb and use it in postmaster process(_pg_init) only but
> not in any other background processes.
> 
> 
>  But if we do not pre-load shared library(removing entry from
> shared_preload_libraries in .conf file), everything works fine (We were
> able to open badger db, put, get etc.. from any process)
> 
>  As we are not aware of how postgres loads and manages its shared library
> things, we couldn't figure out the issue exactly. Your suggestions are
> valuable.
> 
> Thanks & Regards,
> Abinaya KR

What precisely are you trying to do here, and how are you doing it?
Is the source published somewhere?

Best,
David.
-- 
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Speed up the removal of WAL files
Next
From: Curt Tilmes
Date:
Subject: Re: [PATCH] Find additional connection service files inpg_service.conf.d directory