Re: Materialized views WIP patch - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Materialized views WIP patch
Date
Msg-id 5123A1E0.70405@gmx.net
Whole thread Raw
In response to Re: Materialized views WIP patch  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Materialized views WIP patch
List pgsql-hackers
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.




pgsql-hackers by date:

Previous
From: Ants Aasma
Date:
Subject: Re: 9.2.3 crashes during archive recovery
Next
From: Tomas Vondra
Date:
Subject: Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system