| From: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
|---|---|
| To: | Pavel <baros(dot)p(at)seznam(dot)cz> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Snapshot Materialized Views - GSoC |
| Date: | 2010-05-20 17:35:22 |
| Message-ID: | AANLkTikCPa3CbOemUO4LiYflLwcuwxPcuVpOSuE9ZBGF@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2010/5/20 Pavel <baros(dot)p(at)seznam(dot)cz>:
>
> d) what to do when someone use INSERT, UPDATE or DELETE against MV?
> 1 - raise error? - I prefer this option
+1, FWIW
> 2 - let commands change MV? (no chance to let changes propagate to
> source tables, not for this summer :)
> if pg lets user to DML against MV, I expect that triggers should work too
>
no, if you don't propagate then you don't have a view of the tables
the MV comes from...
error if you'll not implement propagation now
--
Jaime Casanova www.2ndQuadrant.com
Soporte y capacitación de PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-05-20 17:54:20 | Re: Fwd: PGBuildfarm member colugos Branch HEAD Status changed from OK to StartDb-C:3 failure |
| Previous Message | Tom Lane | 2010-05-20 17:33:55 | Re: ExecutorCheckPerms() hook |