Postgres Pro
Downloads
Home   >   mailing lists

Re: CREATE MATERIALIZED VIEW .. FOR UPDATE - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: CREATE MATERIALIZED VIEW .. FOR UPDATE
Date
Msg-id 20130802175603.GP5669@eldon.alvh.no-ip.org
Whole thread Raw
In response to CREATE MATERIALIZED VIEW .. FOR UPDATE  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Next
From: Stephen Frost
Date:
Subject: Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])