| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Robert Haas <robertmhaas(at)gmail(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-20 21:25:50 |
| Message-ID: | 51253F5E.7000703@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 2/20/13 2:30 PM, Kevin Grittner wrote:
>> Are there TRUNCATE triggers on materialized views?
> No. Nor SELECT, INSERT, UPDATE, or DELETE triggers. You can't
> create a trigger of any type on a materialized view. I don't think
> that would interfere with event triggers, though.
More generally, I would consider the invalidation of a materialized view
a DDL command, whereas truncating a table is a DML command. This has
various implications with triggers, logging, permissions. I think it's
not good to mix those two.
Also note that un-invalidating==refreshing a materialized view is
already a DDL command.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2013-02-20 22:03:36 | Re: Materialized views WIP patch |
| Previous Message | Stephen Frost | 2013-02-20 19:35:35 | Re: Materialized views WIP patch |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2013-02-20 21:42:09 | Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system |
| Previous Message | Phil Sorber | 2013-02-20 20:16:56 | Re: [PATCH] Add PQconninfoParseParams and PQconninfodefaultsMerge to libpq |