Added security_invoker option while creating a view. #6371

This commit is contained in:
Anil Sahoo
2023-06-22 11:14:03 +05:30
committed by GitHub
parent 1184752540
commit 78db1e3c36
67 changed files with 1653 additions and 90 deletions
Binary file not shown.

Before

Width:  |  Height:  |  Size: 24 KiB

After

Width:  |  Height:  |  Size: 9.8 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 39 KiB

After

Width:  |  Height:  |  Size: 18 KiB

+4 -1
View File
@@ -39,7 +39,10 @@ Use the fields in the *Definition* tab to define properties of the view:
* Set the *Security Barrier* switch to *Yes* to indicate that the view is to act
as a security barrier. For more information about defining and using a
security barrier rule, see Section 38.5 of the PostgreSQL documentation.
security barrier rule, see Rules and Privileges of the PostgreSQL documentation.
* Set the *Security Invoker* switch to *Yes* to indicate that the underlying base
relations are to be checked against the privileges of the user of the view rather
than the view owner. This option is available from PostgreSQL 15 onwards.
* Use the drop-down listbox next to *Check options* to select from *No*, *Local*
or *Cascaded*: