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

From: "Hou, Zhijie" <houzj(dot)fnst(at)cn(dot)fujitsu(dot)com>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Muhammad Usama <m(dot)usama(at)gmail(dot)com>
Subject: RE: A new function to wait for the backend exit after termination
Date: 2020-12-04 03:13:42
Message-ID: d227d6cf8ec447f6a680c08eebae1957@G08CNEXMBPEKD05.g08.fujitsu.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

- 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)

Best regards,
houzj

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kasahara Tatsuhito 2020-12-04 03:21:44 Re: autovac issue with large number of tables
Previous Message Kyotaro Horiguchi 2020-12-04 03:05:22 Re: Huge memory consumption on partitioned table with FKs