From: | Rich Doughty <rich(at)opusvl(dot)com> |
---|---|
To: | KeithW(at)NarrowPathInc(dot)com |
Cc: | PostgreSQL Perform <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: view of view |
Date: | 2005-12-08 13:46:45 |
Message-ID: | 43983945.9020706@opusvl.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Keith Worthington wrote:
> Hi All,
>
> I am working on an application that uses PostgreSQL. One of the
> functions of the application is to generate reports. In order to keep
> the code in the application simple we create a view of the required data
> in the database and then simply execute a SELECT * FROM
> view_of_the_data; All of the manipulation and most of the time even the
> ordering is handled in the view.
>
> My question is how much if any performance degradation is there in
> creating a view of a view?
>
> IOW if I have a view that ties together a couple of tables and
> manipulates some data what will perform better; a view that filters,
> manipulates, and orders the data from the first view or a view that
> performs all the necessary calculations on the original tables?
from personal experience, if the inner views contain outer joins performance
isn't that great.
--
- Rich Doughty
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Rylander | 2005-12-08 14:00:06 | Re: Memory Leakage Problem |
Previous Message | Merlin Moncure | 2005-12-08 13:13:01 | Re: view of view |