| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(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 12:52:18 |
| Message-ID: | 24006.1221483138@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> Simon Riggs <simon(at)2ndQuadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2008-09-15 12:53:57 | Re: Parsing of pg_hba.conf and authentication inconsistencies |
| Previous Message | Fujii Masao | 2008-09-15 12:42:38 | Re: Synchronous Log Shipping Replication |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-09-15 13:24:23 | Re: rmgr hooks and contrib/rmgr_hook |
| Previous Message | Simon Riggs | 2008-09-15 10:14:29 | Re: rmgr hooks and contrib/rmgr_hook |