Message-ID: <37bda3bc33a441557fd658afc5dfbf3000f06d49.camel@cybertec.at>
Subject: Re: Kill postgresql process
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: abbas alizadeh <ramkly@yahoo.com>, pgsql-admin@lists.postgresql.org
Date: Mon, 14 Jun 2021 18:15:35 +0200
In-Reply-To: <38E1E462-CA29-485F-9AC0-4339B9DB2913@yahoo.com>
References: <38E1E462-CA29-485F-9AC0-4339B9DB2913.ref@yahoo.com>
	 <38E1E462-CA29-485F-9AC0-4339B9DB2913@yahoo.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/37bda3bc33a441557fd658afc5dfbf3000f06d49.camel%40cybertec.at>
Precedence: bulk

On Mon, 2021-06-14 at 23:41 +0800, abbas alizadeh wrote:
> How we can kill the stuck process?
> The process didn’t kill by pg_cancel_backend/pg_terminate_backend.
> Is there any way beside of using “kill -9” or “pg_ctl kill ABRT” ?

If you don't mind a little hackery, I found a simple way to
terminate backends that don't react to interrupts that avoids
"kill -9" and the ensuing crash recovery:

- Attach to the backend with gdb.
- Enter "print ProcessInterrupts()"

Of course that will not work if the backend is in uninterruptible
sleep (for example, stuck in an I/O operation).

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com