| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
| Cc: | JG <vhz95(at)rocketmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Database denormalization |
| Date: | 2012-02-14 19:12:11 |
| Message-ID: | CAOR=d=3kUfiouBQnVAJ497CWnB2Rv77-uSy9MZ+VSuonW2i8rg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Feb 14, 2012 at 6:27 AM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> wrote:
> A materialized view is actually a table that holds a (possibly
> aggregated)
> copy of data from elsewhere in the database.
>
> Apart from materialized views, you can denormalize for performance by
> adding columns to tables that store a copy of information from another
> table,
> with the benefit that you can avoid joins to access the information.
The standard reference for materialized views is the page by j gardner:
http://tech.jonathangardner.net/wiki/PostgreSQL/Materialized_Views
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2012-02-14 19:37:37 | Re: pg_upgrade: out of memory |
| Previous Message | Adrian Klaver | 2012-02-14 14:39:03 | Re: [GENERA]: Postgresql-9.1.1 synchronous replication issue |