From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gregory Stark <stark(at)enterprisedb(dot)com>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: rmgr hooks and contrib/rmgr_hook |
Date: | 2008-09-15 14:01:59 |
Message-ID: | 48CE6AD7.1070605@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Simon Riggs wrote:
> On Mon, 2008-09-15 at 08:52 -0400, Tom Lane wrote:
>> I've never heard of anyone building a non-core index AM at all; much
>> less trying to use it in a production context. Given the obvious
>> potential for version-mismatch-type problems, it's hard to believe
>> that anyone ever would try.
>
> The lack of a chicken is not an argument against the use case for an
> egg.
>
> But in any case, Bizgres was exactly this case, so they already did. We
> just forced the authors to produce a code fork to do it, confusing
> people rather than attracting people to Postgres.
Are you referring to the bitmap index patch? IIRC, there was some
non-trivial changes to indexam API in there, as well as issues with
VACUUM. If anything, that patch supports the assumption that anything
that needs WAL-logging is working at such a low-level that it needs to
be in core anyway.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-09-15 14:04:33 | Re: rmgr hooks and contrib/rmgr_hook |
Previous Message | Gregory Stark | 2008-09-15 13:58:50 | Re: rmgr hooks and contrib/rmgr_hook |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-09-15 14:04:33 | Re: rmgr hooks and contrib/rmgr_hook |
Previous Message | Gregory Stark | 2008-09-15 13:58:50 | Re: rmgr hooks and contrib/rmgr_hook |