Re: rmgr hooks and contrib/rmgr_hook - Mailing list pgsql-hackers

From Tom Lane
Subject Re: rmgr hooks and contrib/rmgr_hook
Date
Msg-id 24006.1221483138@sss.pgh.pa.us
Whole thread Raw
In response to Re: rmgr hooks and contrib/rmgr_hook  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: rmgr hooks and contrib/rmgr_hook  (Gregory Stark <stark@enterprisedb.com>)
Re: rmgr hooks and contrib/rmgr_hook  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Gregory Stark <stark@enterprisedb.com> writes:
> Simon Riggs <simon@2ndQuadrant.com> writes:
>> Indexes have always been able to be added dynamically. Now they can be
>> recovered correctly as well.

> Hm, so currently if you want to add a new indexam you can't just insert into
> pg_am and make them recoverable. You basically have to build in your new index
> access method into Postgres with the new rmgr. That is annoying and a problem
> worth tackling.

I concur with Heikki that that's not exactly a compelling use-case.
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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Fujii Masao"
Date:
Subject: Re: Synchronous Log Shipping Replication
Next
From: Magnus Hagander
Date:
Subject: Re: Parsing of pg_hba.conf and authentication inconsistencies