From: Jeff Davis <pgsql@j-davis.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: bossartn@amazon.com
Cc: pgsql-hackers@postgresql.org
Subject: Re: Allow pg_signal_backend members to use pg_log_backend_memory_stats().
Date: Sun, 24 Oct 2021 20:31:37 -0700
Message-ID: <ab46bf8a5158d27cdbb6901f49a6e38dd23e619e.camel@j-davis.com> (raw)
In-Reply-To: <20211025.115333.563958443822411952.horikyota.ntt@gmail.com>
References: <e5cf6684d17c8d1ef4904ae248605ccd6da03e72.camel@j-davis.com>
<33F34F0C-BB16-48DE-B125-95D340A54AE8@amazon.com>
<d87b3a4fa3dacb103a8f3f50751ec9e638b2e2b1.camel@j-davis.com>
<20211025.115333.563958443822411952.horikyota.ntt@gmail.com>
On Mon, 2021-10-25 at 11:53 +0900, Kyotaro Horiguchi wrote:
> In other words, I don't think pg_signal_backends is not meant to
> control "log something on another session" or "rotate log file".
> It's
> danger that if we allow somewone to rotate log files, that means to
> allow same user to terminate another session.
The current patch doesn't allow members of pg_signal_backend to rotate
the log file.
Do you think pg_signal_backend is the wrong group to allow usage of
pg_log_backend_memory_contexts()? Alternatively, it could simply not
GRANT anything, and leave that up to the administrator to choose who
can use it.
Regards,
Jeff Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: pgsql@j-davis.com, horikyota.ntt@gmail.com, bossartn@amazon.com
Subject: Re: Allow pg_signal_backend members to use pg_log_backend_memory_stats().
In-Reply-To: <ab46bf8a5158d27cdbb6901f49a6e38dd23e619e.camel@j-davis.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox