| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Simon Windsor" <simon(dot)windsor(at)cornfield(dot)me(dot)uk>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Performance of views |
| Date: | 2008-11-03 01:59:32 |
| Message-ID: | dcc563d10811021759o1f73f252h7237aa13fd267e94@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Nov 2, 2008 at 6:39 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Simon,
>
>> * Higher overhead mapping to original tables and indexes
>
> This just plain isn't true in PG, at least, and I'd think most other
> sensible databases..
Note that, at least in older versions, MySQL completely materialized a
temporary table from a view, then used that for the view. This is
horribly inefficient, and results in a lot of people thinking views
are slow. Not sure if this has been addressed in MySQL yet, don't
really care anymore, since I rarely use mysql for anything anymore.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sam Mason | 2008-11-03 02:19:14 | Re: Are there plans to add data compression feature to postgresql? |
| Previous Message | Craig Ringer | 2008-11-03 01:54:18 | Re: Are there plans to add data compression feature to postgresql? |