From: | Matthew Nuzum <mattnuzum(at)gmail(dot)com> |
---|---|
To: | Amit V Shah <ashah(at)tagaudit(dot)com> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Do Views execute underlying query everytime ?? |
Date: | 2005-06-21 14:45:21 |
Message-ID: | f3c0b4080506210745e9a9bb0@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 6/21/05, Amit V Shah <ashah(at)tagaudit(dot)com> wrote:
> Hi all,
...
> I am thinking of having a solution where I create views for each screen,
> which are just read only.
>
> However, I donot know if the query that creates the view is executed
> everytime I select something from the view. Because if that is the case,
> then I think my queries will again be slow. But if that is the way views
> work, then what would be the point in creating them ..
>
> Any suggestions, helps --
They do get executed every time. I have a similar issue, but my data
does not change very frequently, so instead of using a view, I create
lookup tables to hold the data. So once a day I do something like
this:
drop lookup_table_1;
create table lookup_table_1 as SELECT ...;
In my case, rows are not deleted or updated, so I don't actually do a
"drop table..." I merely add new records to the existing table, but if
your data changes, the drop table technique can be faster than doing a
delete or update.
--
Matthew Nuzum
www.bearfruit.org
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2005-06-21 14:48:39 | Re: Do Views execute underlying query everytime ?? |
Previous Message | Tom Lane | 2005-06-21 14:42:53 | Re: Limit clause not using index |