| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | Marti Raudsepp <marti(at)juffo(dot)org>, Reece Hart <reece(at)harts(dot)net>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: automatically refresh all materialized views? |
| Date: | 2014-03-11 19:23:54 |
| Message-ID: | 19088.1394565834@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Kevin Grittner <kgrittn(at)ymail(dot)com> writes:
> Marti Raudsepp <marti(at)juffo(dot)org> wrote:
>> Not always, there may be circular dependencies between them.
> I haven't been able to think of a way to create circular references
> among a set of materialized views, short of committing violence
> against the system catalog tables directly. What have I missed?
It'd be pretty trivial if we had CREATE OR REPLACE MATERIALIZED VIEW.
Which I assume is not there only for lack of round tuits, and not
because you deliberately intend that it will never be implemented.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marti Raudsepp | 2014-03-11 19:42:41 | Re: automatically refresh all materialized views? |
| Previous Message | John R Pierce | 2014-03-11 19:19:24 | Re: replication timeout in pg_basebackup |