Re: Snapshot Materialized Views - GSoC - Mailing list pgsql-hackers

From Jaime Casanova
Subject Re: Snapshot Materialized Views - GSoC
Date
Msg-id AANLkTikCPa3CbOemUO4LiYflLwcuwxPcuVpOSuE9ZBGF@mail.gmail.com
Whole thread Raw
In response to Snapshot Materialized Views - GSoC  (Pavel <baros.p@seznam.cz>)
List pgsql-hackers
2010/5/20 Pavel <baros.p@seznam.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: ExecutorCheckPerms() hook
Next
From: Tom Lane
Date:
Subject: Re: Fwd: PGBuildfarm member colugos Branch HEAD Status changed from OK to StartDb-C:3 failure