Hi, On 2018-02-16 16:03:37 -0800, Andres Freund wrote: > This triggered a failure on rhinoceros, in the sepgsql test: > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rhinoceros&dt=2018-02-16%2023%3A45%3A02 > > The relevant diff is: > + LOG: SELinux: allowed { execute } > scontext=unconfined_u:unconfined_r:sepgsql_regtest_superuser_t:s0-s0:c0.c255 > tcontext=system_u:object_r:sepgsql_proc_exec_t:s0 tclass=db_procedure > name="pg_catalog.int4eq(integer,integer)" > and that's because we now invoke the function access hook for grouping > equal, which we previously didn't. > > I personally think the new behaviour makes more sense, but if somebody > wants to argue differently? The only argument against I can see is that > there's some other cases where also don't yet invoke it, but that seems > weak. > > I never fully grasped the exact use-case for the function execute hook > is, so maybe Kaigai and/or Robert could comment?
Fixed by adjusting the test output: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rhinoceros&dt=2018-02-21%2002%3A45%3A01 Greetings, Andres Freund
