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
any
bad consequences.
Please clarify me, if i'm wrong.
Regards,
Abinaya K
> On Wed, Jan 24, 2018 at 1:24 PM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>
>> On Wed, Jan 24, 2018 at 1:27 PM, Abinaya k <abinaya.k@gmail.com>
>> wrote:
>> > Hai
Hai all,
We are building In-memory index extension for postgres. We would
capture table inserts, updates, deletes using triggers. During vacuum
operation, postgres would give calls to ambulkdelete, amvacuumcleanup (as
part of index cleanup). As we handle all updates, deletes using triggers,
-- Forwarded message --
From: "Abinaya k" <abinaya.k@gmail.com>
Date: Jan 23, 2018 1:43 PM
Subject: Regarding ambulkdelete, amvacuumcleanup index methods
To: <pgsql-hack...@postgresql.org>
Cc:
Hai all,
We are building In-memory index extension
Hai all,
We are building In-memory index extension for postgres. We would
capture table inserts, updates, deletes using triggers. During vacuum
operation, postgres would give calls to ambulkdelete, amvacuumcleanup (as
part of index cleanup). As we handle all updates, deletes using triggers,
