From: | Ivan Novick <inovick(at)pivotal(dot)io> |
---|---|
To: | Abinaya Kajendiran <abinayakajee(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Regarding drop index |
Date: | 2018-01-30 23:57:26 |
Message-ID: | CAPJXddY=sd21h7kruL-EsGGNUh2NEk46nuy5CHPrObEim-Zjgg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Abinaya,
Have you seen some benchmarks showing that an in-memory index will fix some
bottlenecks?
Do you have an idea how much of a gain this will provide?
Can you point to a github repo for it?
Cheers,
Ivan
On Tue, Jan 30, 2018 at 1:12 AM, Abinaya Kajendiran <abinayakajee(at)gmail(dot)com>
wrote:
> Hello all,
>
> We are building in-memory index extension for postgres. For drop index
> query, does postgres notify me through index access methods?
>
> Currently, we are using event triggers to capture drop index. If there is
> a better way, please do suggest.
>
> Thanks in advance.
>
> Regards,
> Abinaya K
>
>
--
Ivan Novick, Product Manager Pivotal Greenplum
inovick(at)pivotal(dot)io -- (Mobile) 408-230-6491
https://www.youtube.com/GreenplumDatabase
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2018-01-31 00:02:51 | Re: [HACKERS] MERGE SQL Statement for PG11 |
Previous Message | Andreas Karlsson | 2018-01-30 23:52:50 | Re: [HACKERS] GSoC 2017: Foreign Key Arrays |