pgsql: Don't reject ROW_MARK_REFERENCE rowmarks for materialized views.

Started by Tom Laneover 12 years ago1 messagescomitters
Jump to latest
#1Tom Lane
tgl@sss.pgh.pa.us

Don't reject ROW_MARK_REFERENCE rowmarks for materialized views.

We should allow this so that matviews can be referenced in UPDATE/DELETE
statements in READ COMMITTED isolation level. The requirement for that
is that a re-fetch by TID will see the same row version the query saw
earlier, which is true of matviews, so there's no reason for the
restriction. Per bug #9398.

Michael Paquier, after a suggestion by me

Branch
------
REL9_3_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/3973034e6dc599de2203ed812f783a57b63dce5c

Modified Files
--------------
src/backend/executor/execMain.c | 13 +++++++------
src/test/regress/expected/matview.out | 26 ++++++++++++++++++++++++++
src/test/regress/sql/matview.sql | 8 ++++++++
3 files changed, 41 insertions(+), 6 deletions(-)

--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers