Matthew Wilson wrote:
I've heard people talking about using "materialized views" for this, but that was with Oracle.
You can build those manually with PostgreSQL if you really want them: http://wiki.postgresql.org/wiki/Materialized_Views
The fundamental architecture is sound for a lot of problems in this area, you just have to figure out how to build them efficiently. In your case, you might just consider if there's a way way to update the MV in batches, rather than rely on triggers to keep the data up to date, after each data import.
-- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support greg@xxxxxxxxxxxxxxx www.2ndQuadrant.us -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
