| From: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
|---|---|
| To: | "Dann Corbit" <DCorbit(at)connx(dot)com> |
| Cc: | "Ashish Karalkar" <ashish(dot)karalkar(at)info-spectrum(dot)com>, "Andrej Ricnik-Bay" <andrej(dot)groups(at)gmail(dot)com>, "Ron Johnson" <ron(dot)l(dot)johnson(at)cox(dot)net>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Views- Advantages and Disadvantages |
| Date: | 2007-05-09 19:14:17 |
| Message-ID: | 6A1520DB-897D-42F7-BDAA-7884983D58DF@seespotcode.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On May 9, 2007, at 14:02 , Dann Corbit wrote:
> Views can hide important information from the optimizer (especially
> index information).
Really? AIUI, views—at least in PostgreSQL—are implemented using
PostgreSQL's rule system: the entire query is rewritten to include
the view query, and the optimizer sees the rewritten query. What the
optimizer sees is the same as if the view were inlined in the
original query.
Michael Glaesemann
grzm seespotcode net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tilmann Singer | 2007-05-09 19:26:09 | Re: Audit-trail engine: getting the application's layer user_id |
| Previous Message | Marcelo de Moraes Serpa | 2007-05-09 19:11:08 | Re: Audit-trail engine: getting the application's layer user_id |