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

From: Bill Moseley <moseley(at)hank(dot)org>
To: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Performance issues of one vs. two split tables.
Date: 2007-05-15 05:22:55
Message-ID: 20070515052254.GA24323@hank.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, May 15, 2007 at 06:33:26AM +0200, Dawid Kuroczko wrote:
> Well, views are not going to help with memory consumption here.
> It is the table contents that gets cached in buffer cache, not the
> views contents. So if you have a view which returns only one
> column from 15-column table, you will be caching that 15-column
> data nonetheless. View, as the name states, is converted into
> a select on a real table.

Are you saying that in Postgresql:

select first_name, last_name from user_table;

uses the same memory as this?

select first_name, last_name,
passowrd, email,
[10 other columns]
from user_table;

--
Bill Moseley
moseley(at)hank(dot)org

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dawid Kuroczko 2007-05-15 05:51:44 Re: Performance issues of one vs. two split tables.
Previous Message Dawid Kuroczko 2007-05-15 04:33:26 Performance issues of one vs. two split tables.