From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Remaining beta blockers |
Date: | 2013-04-30 17:12:14 |
Message-ID: | 517FFB6E.8010807@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2013-04-30 17:45:48 | Re: Remaining beta blockers |
Previous Message | Greg Smith | 2013-04-30 17:05:30 | Re: Substituting Checksum Algorithm (was: Enabling Checksums) |