Robert Haas <robertmh...@gmail.com> writes:
> On Tue, Feb 19, 2013 at 11:01 AM, Peter Eisentraut <pete...@gmx.net> wrote:
>> This might be different if there were a command to refresh all
>> materialized views, because you don't want to have to go around and type
>> separate commands 47 times after a restore.
> Well, it's pretty easy to do:
> SELECT 'LOAD MATERIALIZED VIEW ' || p.oid::regclass || ';' FROM
> pg_class WHERE relkind = 'm';
> ...but we could also add explicit syntax for it, perhaps along the
> lines of what we have for CLUSTER and VACUUM.
It's not really that easy, because of the likelihood that MVs have to be
refreshed in a specific order. The SELECT you suggest definitely seems
too simplistic. A dedicated command could perhaps be built to pay
attention to dependencies ... but if we're still coding such things now,
it seems a bit late for 9.3.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
