| From: | Mag Gam <magawake(at)gmail(dot)com> |
|---|---|
| To: | Christophe <xof(at)thebuild(dot)com> |
| Cc: | PostgreSQL general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Column oriented pgsql |
| Date: | 2009-05-09 01:09:54 |
| Message-ID: | 1cbd6f830905081809s7a46a418g4ce8fea74619b21d@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 | John R Pierce | 2009-05-09 01:25:24 | Re: Column oriented pgsql |
| Previous Message | Alvaro Herrera | 2009-05-08 21:40:48 | Re: limit-offset different result sets with same query |