From: | "bfriedman(dot)postgresql" <bfriedman(dot)postgresql(at)gmail(dot)com> |
---|---|
To: | Mag Gam <magawake(at)gmail(dot)com> |
Cc: | Christophe <xof(at)thebuild(dot)com>, PostgreSQL general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Column oriented pgsql |
Date: | 2009-05-09 01:47:48 |
Message-ID: | 4A04E0C4.7040201@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
If you are looking for a column based dbms, you might want to check out
Monet - it is a columnar database.
For some applications, columnar databases can be much faster than
traditional rdbms systems. However, column based databases are not a
'one size fits all' answer.
Brent Friedman
Mag Gam wrote:
> Got it thanks!
>
>
>
> On Fri, May 8, 2009 at 2:57 PM, Christophe <xof(at)thebuild(dot)com> wrote:
>
>> On May 8, 2009, at 11:25 AM, John R Pierce wrote:
>>
>>> you read your tables by column, rather than by row??
>>> SQL queries are inherently row oriented, the fundamental unit of storage
>>> is a 'tuple', which is a representation of a row of a table.
>>>
>> I believe what is referring to is the disk storage organization, clustering
>> a single column from multiple rows together onto a page. For example, if
>> your typical use of a table is to read one particular column from a large
>> number of rows, this could (in theory) improve performance.
>>
>> AFAIK, PostgreSQL doesn't support this.
>>
>> --
>> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-general
>>
>>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2009-05-09 01:59:37 | Re: limit-offset different result sets with same query |
Previous Message | John R Pierce | 2009-05-09 01:25:24 | Re: Column oriented pgsql |