Hiroshi Inoue wrote:
Heikki Linnakangas wrote:
Hiroshi Inoue wrote:
Concurrently updating an updatable view seems to cause
an unexpected result. Is it a known issue?
Looks right to me. What did you expect?
Shouldn't the last response
(session-2)
UPDATE 1
be
(seesion-2)
UPDATE 0
?
Ah, I re-read the example and I see what you mean now.
The problem is that the new tuple version is checked only against the
condition in the update rule, id=OLD.id, but not the condition in the
original update-claus, dt='a'.
Yeah, that's confusing :(.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
