On Tue, Apr 13, 2021 at 10:33 AM Dave Page <dpage@pgadmin.org> wrote:
> On a system with selinux and sepgsql configured, search path resolution appears to fail if sepgsql is in enforcing
mode,but selinux is in permissive mode (which, as I understand it, should cause sepgsql to behave as if it's in
permissivemode anyway - and does for other operations). Regardless of whether my understanding of the interaction of
thetwo permissive modes is correct, I don't believe the following should happen:
I agree that this sounds like something which shouldn't happen if the
system is in permissive mode, but I think the behavior itself is
deliberate. See OAT_NAMESPACE_SEARCH and commit
e965e6344cfaff0708a032721b56f61eea777bc5.
--
Robert Haas
EDB: http://www.enterprisedb.com