Re: [PATCH] pg_reload_backend to signal SIGHUP to a specific backend

From: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
To: Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] pg_reload_backend to signal SIGHUP to a specific backend
Date: 2017-06-29 07:49:46
Message-ID: CA+q6zcVUpwU3t5LFVTswVGU-9S_m0vgwuvavY7JSyG=Wfyro5A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 29 Jun 2017 08:18, "Yugo Nagata" <nagata(at)sraoss(dot)co(dot)jp> 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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message sanyam jain 2017-06-29 08:32:19 Start logical decoding from any lsn present in the wal segment
Previous Message Yugo Nagata 2017-06-29 06:49:20 Re: [PATCH] pg_reload_backend to signal SIGHUP to a specific backend