| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Ries van Twisk <ries(at)jongert(dot)nl> |
| Cc: | <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: To use a VIEW or not to use a View..... |
| Date: | 2003-01-22 16:10:04 |
| Message-ID: | 20030122080733.Y96911-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Wed, 22 Jan 2003, Ries van Twisk wrote:
> Dear PostgreSQL users,
>
> I have a view and a table,
>
> I understand that when a frontend accesses a VIEW that PostgreSQL cannot use
> a index on that view.
> For example when I do this: SELECT * FROM full_cablelist WHERE
> projectocode=5; Correct?
In general, no. There are some exceptions, for example views using
EXCEPT I believe will not push conditions down. In 7.2.x, views using
any of the set ops (INTERSECT, UNION, EXCEPT) wouldn't push conditions
down. There are a few other such conditions, but for your view, I think
this isn't going to be an issue.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomasz Myrta | 2003-01-22 16:20:57 | Re: To use a VIEW or not to use a View..... |
| Previous Message | Bruno Wolff III | 2003-01-22 15:48:10 | Re: To use a VIEW or not to use a View..... |