From: | abbas alizadeh <ramkly(at)yahoo(dot)com> |
---|---|
To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Kill postgresql process |
Date: | 2021-06-14 16:32:40 |
Message-ID: | C26A3E91-96C6-41A7-BD6E-3FF203BDFC5D@yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
The query was called by web server, It was connected to database through socket and connection wasn’t terminate. I tried to close the connection, but it didn’t work.
Postgres version is 9.2 for this case.
We use postgis and pg_repack
> On 14 Jun 2021, at 11:49 PM, Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
>
> On Mon, Jun 14, 2021 at 11:41 PM abbas alizadeh <ramkly(at)yahoo(dot)com> 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” ?
>
> pg_cancel_backend / pg_terminate_backend is the normal way to do that.
> If it's not working it means there's something going on. Is it a
> regular backend, and if yes what query is it executing?
>
> Do you have any 3rd party extensions, and what is the postgres versions?
>
> If could also help to get a stack trace:
> https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Wells Oliver | 2021-06-14 16:50:48 | pg_restore, custom setting, and materialized view -- performance question |
Previous Message | Julien Rouhaud | 2021-06-14 16:25:23 | Re: Kill postgresql process |