> what happens to sessions is that it does:
>
> SELECT session_data, id
> FROM sessions
> WHERE id = ?
> FOR UPDATE
>
> .... client does some processing ...
>
> UPDATE sesssions set session_data = ? WHERE id = ?;
>
> (this is where the error happens)
>
> I think part of my problem might be that sessions is a view
> and not a table,
Did you create an on update do instead rule ?
This is currently not done automatically for views,
thus views without additional "create rule"s are select only.
But, I am wondering whether the "for update" places the correct lock ?
Andreas
