From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Pluggable Indexes (was Re: rmgr hooks (v2)) |
Date: | 2009-01-22 07:12:13 |
Message-ID: | 49781C4D.30407@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Simon Riggs wrote:
> Without the patch it is completely *impossible* to write an index plugin
> that is *recoverable*.
It's also impossible to do many other things without modifying the
source code. Bitmap indexam had to do it, my clustered indexes had to do
it, GIN had to do it.
> Yes, we have pluggable indexes now, but unless
> they are recoverable we certainly can't ever use them in production.
Sure you can. Just Do It, if that's what you want. If you're willing to
write a custom indexam, and run it in production, compiling PostgreSQL
from source and patching it isn't such a stretch.
Don't get me wrong, I'm certainly not against pluggable indexes in
principle. I just don't believe this patch brings us closer to that goal
in any significant way.
> With the patch, you still have to write the index code. I agree it is
> hard code to write, but not impossible. I would go so far as to say that
> the patch helps you 0% with the task of actually writing the plugin. But
> the patch enables you to start and that is all its intended as: an
> enabler.
Nothing stops you from starting right now, without this plugin. This is
open source.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2009-01-22 07:35:53 | Re: WIP: Automatic view update rules |
Previous Message | Jeff Davis | 2009-01-22 06:18:58 | Re: Lock conflict behavior? |