Noah Misch f3ab5d4696 Switch user ID to the object owner when populating a materialized view. ...

This makes superuser-issued REFRESH MATERIALIZED VIEW safe regardless of
the object's provenance.  REINDEX is an earlier example of this pattern.
As a downside, functions called from materialized views must tolerate
running in a security-restricted operation.  CREATE MATERIALIZED VIEW
need not change user ID.  Nonetheless, avoid creation of materialized
views that will invariably fail REFRESH by making it, too, start a
security-restricted operation.

Back-patch to 9.3 so materialized views have this from the beginning.

Reviewed by Kevin Grittner.

2013-07-12 18:21:22 -04:00

..

sgml

Switch user ID to the object owner when populating a materialized view.

2013-07-12 18:21:22 -04:00

Makefile

Add maintainer-check target

2011-03-28 22:56:52 +03:00