Re: pgsql: Include permissive/enforcing state in sepgsql log messages.

From: Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Include permissive/enforcing state in sepgsql log messages.
Date: 2022-01-13 13:03:15
Message-ID: CANbhV-FXiQb=Tn9pHYixzErTgfUCdqH1c4AJ0zbAUg-LO3KtVQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, 12 Jan 2022 at 19:23, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Include permissive/enforcing state in sepgsql log messages.
>
> SELinux itself does this (at least in modern releases), and it
> seems like a good idea to reduce confusion.
>
> Dave Page
>
> Discussion: https://postgr.es/m/CA+OCxowsQoLEYc=jN7OtNvOdX0Jg5L7nMYt++=k0X78HGq-sXg@mail.gmail.com
>
> Branch
> ------
> master
>
> Details
> -------
> https://git.postgresql.org/pg/commitdiff/134d9746364425e437a6d8eb1e2de0f3c59bfd2b

Is that a bug fix to be backpatched, or a new/changed feature to be documented?

--
Simon Riggs http://www.EnterpriseDB.com/

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2022-01-13 15:13:46 Re: pgsql: Include permissive/enforcing state in sepgsql log messages.
Previous Message Michael Paquier 2022-01-13 07:18:58 pgsql: Improve error handling of HMAC computations