| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: patch: SQL/MED(FDW) DDL |
| Date: | 2010-09-16 02:05:00 |
| Message-ID: | 29640.1284602700@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> writes:
> On 16/09/10 13:22, Tom Lane wrote:
>> What exactly do those get you that an ordinary index, or at worst an
>> index-organized table, doesn't get you?
> It is pretty rare to see key value stores vs relational engines
> discussed without a descent into total foolishiness, but this Wikipedia
> page looks like a reasonable summary:
> http://en.wikipedia.org/wiki/NoSQL
That doesn't do anything at all to answer my question. I don't want
to debate NoSQL versus traditional RDBMS here. What I asked was:
given that PG is a traditional RDBMS, what exactly are you hoping
to accomplish by putting a key-value storage mechanism in it? And
if you did, how would that be different from an index-organized table?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-09-16 02:05:49 | Re: patch: SQL/MED(FDW) DDL |
| Previous Message | Itagaki Takahiro | 2010-09-16 01:53:43 | Re: Basic JSON support |