diff options
| author | Noah Misch <noah@leadboat.com> | 2013-07-12 18:21:22 -0400 |
|---|---|---|
| committer | Noah Misch <noah@leadboat.com> | 2013-07-12 18:25:41 -0400 |
| commit | fb7c0ac42e1a8e3cde74e83e2c758ada8c62a35e (patch) | |
| tree | b1d0681b57e7db1524b7afa9ae968ba536eabe8b /src/bin/pg_dump/parallel.c | |
| parent | 7484f89daa33477e0027a86ae772f44fa99224ed (diff) | |
| download | postgresql-fb7c0ac42e1a8e3cde74e83e2c758ada8c62a35e.tar.gz postgresql-fb7c0ac42e1a8e3cde74e83e2c758ada8c62a35e.zip | |
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.
Diffstat (limited to 'src/bin/pg_dump/parallel.c')
0 files changed, 0 insertions, 0 deletions