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-28 11:35:12
Message-ID: CA+q6zcX59yZ0LSEnzs3YuYXLc+EXKawYsOzcnPYr--sEgJzwJQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 28 June 2017 at 12:17, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> 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, why this function returns something
different from bool when I'm passing null as an argument?

=# select pg_reload_backend(27961);
WARNING: PID 27961 is not a PostgreSQL server process
WARNING: failed to send signal to backend: 27961
pg_reload_backend
-------------------
f
(1 row)

=# select pg_reload_backend(27962);
pg_reload_backend
-------------------
t
(1 row)

=# select pg_reload_backend(null);
pg_reload_backend
-------------------

(1 row)

Also for some reason I can't grant an execute permission on this function,
am I doing something wrong?

=# grant execute on function pg_reload_backend() to test_user;
ERROR: function pg_reload_backend() does not exist
=# grant execute on function pg_reload_conf() to test_user;
GRANT

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Khandekar 2017-06-28 11:43:19 Re: UPDATE of partition key
Previous Message Daniel Gustafsson 2017-06-28 10:38:42 Re: pg_receivewal and messages printed in non-verbose mode