Re: Performance issues of one vs. two split tables.

From: PFC <lists(at)peufeu(dot)com>
To: "Bill Moseley" <moseley(at)hank(dot)org>, "Postgres General" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Performance issues of one vs. two split tables.
Date: 2007-05-15 16:49:07
Message-ID: op.tsdnn5j2cigqcu@apollo13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


> SELECT o.id
> FROM order o
> JOIN customer c on o.customer = c.id
>
> Does that bring into memory all columns from both order and customer?
> Maybe that's not a good example due to indexes.

No, it just pulls the columns you ask from the table, nothing less,
nothing more.

Splitting tables (vertical partitioning) is used to reduce the size of
the working set that has to fit in RAM... this is a different reason than
what you're thinking about.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Marco Colombo 2007-05-15 17:12:15 Re: a few questions on backup
Previous Message Richard Huxton 2007-05-15 16:46:59 Re: I have some problems while installing PostgreSQL