Re: A new function to wait for the backend exit after termination

Поиск
Список
Период
Сортировка
От Bharath Rupireddy
Тема Re: A new function to wait for the backend exit after termination
Дата
Msg-id CALj2ACVNxfKzwZUZWRKUmVuVuGCOa=CdYz5vNpyk9Q+-jC=j_g@mail.gmail.com
обсуждение исходный текст
Ответ на RE: A new function to wait for the backend exit after termination  ("Hou, Zhijie" <houzj.fnst@cn.fujitsu.com>)
Ответы RE: A new function to wait for the backend exit after termination  ("Hou, Zhijie" <houzj.fnst@cn.fujitsu.com>)
Список pgsql-hackers
On Fri, Dec 4, 2020 at 8:44 AM Hou, Zhijie <houzj.fnst@cn.fujitsu.com> wrote:
>
> -        however only superusers can terminate superuser backends.
> +        however only superusers can terminate superuser backends. When no
> +        <parameter>wait</parameter> and <parameter>timeout</parameter> are
> +        provided, only SIGTERM is sent to the backend with the given process
> +        ID and <literal>false</literal> is returned immediately. But the
>
> I test the case when no wait and timeout are provided.
> True is returned as the following which seems different from the doc.
>
> postgres=# select pg_terminate_backend(pid);
>  pg_terminate_backend
> ----------------------
>  t
> (1 row)
>

Thanks for pointing that out. I reworded that statement. Attaching v5 patch. Please have a look.

With Regards,
Bharath Rupireddy.
EnterpriseDB: http://www.enterprisedb.com

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Kyotaro Horiguchi
Дата:
Сообщение: Re: Wrong statistics for size of XLOG_SWITCH during pg_waldump.
Следующее
От: Amit Langote
Дата:
Сообщение: Re: Huge memory consumption on partitioned table with FKs