From: | Abinaya k <abinaya(dot)k(dot)496(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Fwd: Regarding ambulkdelete, amvacuumcleanup index methods |
Date: | 2018-01-23 16:37:49 |
Message-ID: | CAEtC32P1gcmK4SHUHATRsCR9ZV8ynk+ShnKqy7qu3AQ4-MoCdQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
---------- Forwarded message ----------
From: "Abinaya k" <abinaya(dot)k(dot)496(at)gmail(dot)com>
Date: Jan 23, 2018 1:43 PM
Subject: Regarding ambulkdelete, amvacuumcleanup index methods
To: <pgsql-hackers(at)postgresql(dot)org>
Cc:
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,
we don't have to do any index cleanup in ambulkdelete. But, what stats
should i return from ambulkdelete and amvacuumcleanup? Is that necessary to
return stats from ambulkdelete and amvacuumcleanup ?
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2018-01-23 16:40:01 | Re: PATCH: Configurable file mode mask |
Previous Message | Peter Eisentraut | 2018-01-23 16:33:56 | Re: [HACKERS] taking stdbool.h into use |