| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marko Tiikkaja <pgmail(at)joh(dot)to>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Materialized views WIP patch |
| Date: | 2013-02-19 16:01:36 |
| Message-ID: | 5123A1E0.70405@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Rijkers | 2013-02-19 22:09:13 | Re: Materialized views WIP patch |
| Previous Message | Nicolas Barbier | 2013-02-19 14:24:28 | Re: Materialized views WIP patch |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2013-02-19 16:58:28 | Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system |
| Previous Message | Ants Aasma | 2013-02-19 15:41:33 | Re: 9.2.3 crashes during archive recovery |