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

From Abi KR
Subject Regarding shared_preload_libraries (postgresql.conf file)
Date
Msg-id CAOaFgA-=d1hC=6O3EmatXT55u9pZCbcTryzCywX2yu5spE0vLw@mail.gmail.com
Whole thread Raw
Responses Re: Regarding shared_preload_libraries (postgresql.conf file)  (David Fetter <david@fetter.org>)
Re: Regarding shared_preload_libraries (postgresql.conf file)  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List pgsql-hackers
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

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Cache invalidation after authentication (on-the-fly role creation)
Next
From: Jesper Pedersen
Date:
Subject: Re: Speeding up INSERTs and UPDATEs to partitioned tables