Re: Regarding shared_preload_libraries (postgresql.conf file)

2018-07-05 Thread Andrew Gierth
> "Abi" == Abi KR writes: Abi> hello everyone, Abi> We wanted to make use of embedded key-value store(BadgerDB - Abi> implemented in golang) to save the data related to our extension. Abi> The problem is, when we load our extension using Abi> shared_preload_libraries, we could able to o

Re: Regarding shared_preload_libraries (postgresql.conf file)

2018-07-05 Thread David Fetter
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,

Regarding shared_preload_libraries (postgresql.conf file)

2018-07-05 Thread Abi KR
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_in

Regarding shared_preload_libraries (postgresql.conf file)

2018-07-05 Thread Abinaya k
hello everyone, We are building in-memory index extension for postgres. It makes use of another third-party embedded key-value store (*BadgerDB* - implemented in golang) to store secondary indexes. The problem is