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

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

Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> writes:
> Is that a bug fix to be backpatched, or a new/changed feature to be documented?

It'd be the latter, if sepgsql had any documentation about the
content of its log messages. But AFAICS it doesn't (and I'm not
volunteering to add that).

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2022-01-13 17:01:08 Re: pgsql: Check for STATUS_DELETE_PENDING on Windows.
Previous Message Simon Riggs 2022-01-13 13:03:15 Re: pgsql: Include permissive/enforcing state in sepgsql log messages.