Robert, > - The data can be used if the matview is fully up-to-date. > - The data can be used if the matview is not out of date by more than > a certain amount of time. > - The data can be used if the matview is out of date with respect to > one of its base tables, but not if it is out of date with respect to > another of its base tables. For example, maybe you're OK with using > an order-summary view if new orders have arrived (but not if the view > is more than a day out of date); but not if any customers have been > renamed.
We discussed this around the beginning of CF4. For some reason (which I didn't quite understand at the time), the consensus was that creating a "matview last updated" timestamp was not implementable for 9.3 and would need to wait for 9.4. Again, all of this points to additional columns, or at least relopts, in pg_class. Why is that off the table? -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
