Normalizing denormalization with materialized views

From: "Robert James" <srobertjames(at)gmail(dot)com>
To: "Postgres General" <pgsql-general(at)postgresql(dot)org>
Subject: Normalizing denormalization with materialized views
Date: 2008-03-11 17:19:01
Message-ID: e09785e00803111019m5e197fb8l613a49fb6b00ebb5@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

When forced to denormalize for performance reasons, how do you ensure data
integrity? I like to, instead of denormalizing, use materialized views,
which offer lots of the same benefits without the costs. Yet, in Postgres
they're only experimental add-ons, not to be relied on for production use.

Is there a timetable for supporting materialized views in Postgres proper?
Are other people interested in them (it's #1 on my miss-from-Oracle list)?
What other solutions do people use? (Triggers could work well, if they're
done right)

SRJ

Browse pgsql-general by date

  From Date Subject
Next Message Joshua 2008-03-11 17:26:49 basic plpgsql / sql funtion question
Previous Message Kynn Jones 2008-03-11 17:18:25 Re: ISO something like "#if 0 ... #endif" for SQL code