> On 29 Jun 2017 08:18, "Yugo Nagata" wrote:
>
> This is because this function is defined as strict
Yes, I realized that few moments after I sent my message.
> Arg type is needed.
>
> =# grant execute on function pg_reload_backend(int) to test_user;
Oh, I see, thank you.
On Wed, 28 Jun 2017 13:59:51 +0200
Remi Colinet wrote:
> Hi Yugo,
>
> The patch looks fine. Installed and tested.
Thank you for your interest.
>
> But a similar function already exists for the Postmaster process.
>
> Datum
> pg_reload_conf(PG_FUNCTION_ARGS)
> {
> if (kill(PostmasterP
On Wed, 28 Jun 2017 13:35:12 +0200
Dmitry Dolgov <9erthali...@gmail.com> wrote:
> > On 28 June 2017 at 12:17, Yugo Nagata wrote:
> >
> > Hi,
> >
> > Attached is a patch of pg_reload_backend that is a function signaling
> > SIGHUP to a specific backend. The original idea is from Michael
> Paquier[
Hi Yugo,
The patch looks fine. Installed and tested.
But a similar function already exists for the Postmaster process.
Datum
pg_reload_conf(PG_FUNCTION_ARGS)
{
if (kill(PostmasterPid, SIGHUP))
{
ereport(WARNING,
(errmsg("failed to s
> On 28 June 2017 at 12:17, Yugo Nagata wrote:
>
> Hi,
>
> Attached is a patch of pg_reload_backend that is a function signaling
> SIGHUP to a specific backend. The original idea is from Michael
Paquier[1].
> The documatation isn't included in this patch yet.
I have few questions. I'm curious, wh
Hi,
Attached is a patch of pg_reload_backend that is a function signaling
SIGHUP to a specific backend. The original idea is from Michael Paquier[1].
The documatation isn't included in this patch yet.
We can change some parameters of other backend using the function
as bellow.
postgres=# alter s
