| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Cc: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Pluggable storage |
| Date: | 2017-07-19 17:53:24 |
| Message-ID: | CA+TgmobYmdAzfXAmug8D9Z4qwgietVxJJUqqiGePx9t+-e8mxw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Jul 15, 2017 at 6:36 PM, Alexander Korotkov
<a(dot)korotkov(at)postgrespro(dot)ru> wrote:
> I think in general there are two ways dealing with out index AM API
> limitation. One of them is to extend index AM API.
That's pretty much what I have in mind. I think it's likely that if
we end up with, say, 3 kinds of heap and 12 kinds of index, there will
be some compatibility matrix. Some index AMs will be compatible with
some heap AMs, and others won't be. For example, if somebody makes an
IOT-type heap using the API proposed here or some other one, BRIN
probably won't work at all. btree, on the other hand, could probably
be made to work, perhaps with some greater or lesser degree of
modification.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-07-19 17:56:49 | Re: Pluggable storage |
| Previous Message | Justin Pryzby | 2017-07-19 17:45:07 | PG10b2: column-list UPDATE syntax fails with single column |