| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Abinaya Kajendiran <abinayakajee(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Regarding drop index |
| Date: | 2018-01-31 00:36:35 |
| Message-ID: | 9ee2ca9b-df5a-2b32-754d-0215dabb819c@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/30/18 04:12, Abinaya Kajendiran wrote:
> We are building in-memory index extension for postgres. For drop
> index query, does postgres notify me through index access methods?
No, the access methods just write into blocks for the file they are told
about. The deleting of that file is not handled by the access methods.
> Currently, we are using event triggers to capture drop index. If there
> is a better way, please do suggest.
An event trigger will probably do for now. But you are venturing into
uncharted territory, so you will have to find your own best solution.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2018-01-31 00:44:02 | Re: FOR EACH ROW triggers on partitioned tables |
| Previous Message | Andreas Karlsson | 2018-01-31 00:36:01 | Re: [HACKERS] GnuTLS support |