Horton

Re: sepgsql logging

Andrew Dunstan <andrew@dunslane.net>

View thread View on postgr.es
From: Andrew Dunstan <andrew@dunslane.net>
To: Dave Page <dpage@pgadmin.org>, Jacob Champion <pchampion@vmware.com>
Cc: "robertmhaas@gmail.com" <robertmhaas@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, "tgl@sss.pgh.pa.us" <tgl@sss.pgh.pa.us>
Date: 2022-01-11T16:31:19Z
Lists: pgsql-hackers 
On 1/11/22 10:40, Dave Page wrote:
>
>
>     On Wed, 2021-04-14 at 09:49 -0400, Robert Haas wrote:
>     > Looks superficially reasonable on first glance, but I think we
>     should
>     > try to get an opinion from someone who knows more about SELinux.
>
>     I am not that someone, but this looks straightforward, it's been
>     stalled for a while, and I think it should probably go in.
>
>
> I'd like to see that. Thanks for the review. 
>

I am not that person either. I agree this looks reasonable, but I also
would like the opinion of an expert, if we have one.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

Commits

  1. Include permissive/enforcing state in sepgsql log messages.