This is a document for PGroonga 2.X and 3.X. See PGroonga 1.x document when you're using old PGroonga.
pgroonga.enable_row_level_security
parameterSince 3.1.6.
pgroonga.enable_row_level_security
parameter controls whether logs are output according to pgroonga.log_level
parameter or only critical
logs.
The default is on
, so for tables with Row Security Policies set, PGroonga will only log critical
.
Note:
If this parameter is set to off
, information related to the target row may be included in logs and error messages when some conditions overlap.
In that case, there are security risks.
PostgreSQL Row Security Policies settings and the setting of this parameter are independent of each other.
Setting this parameter to off
does not disable the PostgreSQL Row Security Policies setting.
In SQL:
SET pgroonga.enable_row_level_security = boolean;
In postgresql.conf
:
pgroonga.log_level = boolean
boolean
is a boolean value. There are some literals for boolean value such as on
, off
, true
, false
, yes
and no
.
Here is an example SQL of outputting PGroonga logs according to pgroonga.log_level
parameter, even for a table with Row Security Policies set:
SET pgroonga.enable_row_level_security = off;
Here is an example configuration of outputting PGroonga logs according to pgroonga.log_level
parameter, even for a table with Row Security Policies set:
pgroonga.enable_row_level_security = off;