From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, SAKAMOTO Masahiko <sakamoto(dot)masahiko(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: patch: SQL/MED(FDW) DDL |
Date: | 2010-09-16 00:57:32 |
Message-ID: | AANLkTi=pn_n1d3Y+MbzNoA+ipv=vcDU6HLPQOMRn1vbf@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Sep 15, 2010 at 8:53 PM, Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> wrote:
> 2010/9/16 Robert Haas <robertmhaas(at)gmail(dot)com>:
>> On Wed, Sep 15, 2010 at 3:00 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Yet there are other cases that probably *could* work well based on a
>>> storage-level abstraction boundary; index-organized tables for instance.
>>> So I think we need to have some realistic idea of what we want to
>>> support and design an API accordingly, not hope that if we don't
>>> know what we want we will somehow manage to pick an API that makes
>>> all things possible.
>>
>> Agreed. Random ideas: index-organized tables...
>
> I'd love to see a table that is based on one of the existing KVSs.
I'm not familiar with the term KVS?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-09-16 01:05:08 | Re: patch: SQL/MED(FDW) DDL |
Previous Message | Hitoshi Harada | 2010-09-16 00:53:27 | Re: patch: SQL/MED(FDW) DDL |