From: abbas alizadeh <ramkly@yahoo.com>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Julien Rouhaud <rjuju123@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Kill postgresql process
Date: Fri, 18 Jun 2021 22:33:08 +0800
Message-ID: <86429A65-AF41-40D4-8B7C-FDF6E45742A9@yahoo.com> (raw)
In-Reply-To: <05a195d0d4fc09c4552551e806fd7692b9804e24.camel@cybertec.at>
References: <05a195d0d4fc09c4552551e806fd7692b9804e24.camel@cybertec.at>
Thanks Laurenz, Julien
Stack trace helps alot to find a stuck point.
That AbortCurrentTransaction wirked as well.
Regards
Abbas
> On 15 Jun 2021, at 3:01 PM, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
>
> 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
>
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ramkly@yahoo.com, laurenz.albe@cybertec.at, rjuju123@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Kill postgresql process
In-Reply-To: <86429A65-AF41-40D4-8B7C-FDF6E45742A9@yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox