Re: CREATE MATERIALIZED VIEW .. FOR UPDATE

I just realized I mixed two different (but related) cases in my previous
email:

Alvaro Herrera wrote:
> Does the combination in $SUBJECT make sense?  It is currently allowed,
> but of course the underlying locks only last while the creating
> transaction is open, and they are reacquired during a refresh.

This paragraph is talking about a FOR UPDATE clause in the CREATE
MATERIALIZED VIEW command, as in the email subject.

> Somewhat related is that the error message they emit is a bit
> nonstandard:
> 
> cannot lock rows in materialized view \"%s\"

This other paragraph, and everything below it, is talking about a
SELECT .. FROM matview FOR UPDATE
command.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services