On 2/19/13 8:54 AM, Robert Haas wrote: > In the department of crazy ideas, what about having pg_dump NEVER > refresh ANY materialized views?
It might be useful to have an option for this, but I don't think it should be the default. The default should be that the new database is "ready to go". Then again, when would you ever actually use that option? 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. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
