Message-ID: <05a195d0d4fc09c4552551e806fd7692b9804e24.camel@cybertec.at>
Subject: Re: Kill postgresql process
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Julien Rouhaud <rjuju123@gmail.com>
Cc: abbas alizadeh <ramkly@yahoo.com>, Pgsql-admin
	 <pgsql-admin@lists.postgresql.org>
Date: Tue, 15 Jun 2021 09:01:12 +0200
In-Reply-To: 
 <CAOBaU_bSNffGTF8s8mis28DDUOT1e2xC2cEhdHxEGLj5wAg=_w@mail.gmail.com>
References: <38E1E462-CA29-485F-9AC0-4339B9DB2913.ref@yahoo.com>
	 <38E1E462-CA29-485F-9AC0-4339B9DB2913@yahoo.com>
	 <37bda3bc33a441557fd658afc5dfbf3000f06d49.camel@cybertec.at>
	 <CAOBaU_bSNffGTF8s8mis28DDUOT1e2xC2cEhdHxEGLj5wAg=_w@mail.gmail.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/05a195d0d4fc09c4552551e806fd7692b9804e24.camel%40cybertec.at>
Precedence: bulk

On Tue, 2021-06-15 at 00:25 +0800, Julien Rouhaud wrote:
> Le mar. 15 juin 2021 à 00:15, Laurenz Albe:
> > - 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).
> 
> that may be a terrible idea and leave a buffer pinned or something.
>  and if it's not it won't tell us where we're missing a CALL_FOR_INTERRUPTS

If there is an error, AbortCurrentTransaction() gets called, which releases
all buffer pins.  If you were stuck in an endless loop in a critical
section, you are going to crash anyway.

If you want to investigate where you are stuck, run a backtrace first.

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