On Tue, Jan 10, 2017 at 1:39 PM, Melvin Davidson
wrote:
> *Why not just kill the blocking process first? Then everything else will
> proceed.*
>
That's what he said to do. You can do that with a `SELECT
pg_cancel_backend($pid)` query.
On Tue, Jan 10, 2017 at 1:28 PM, Edmundo Robles
wrote:
> ok, then is better kill one by one!
>
> On Tue, Jan 10, 2017 at 12:16 PM, Melvin Davidson
> wrote:
>
>>
>>
>> On Tue, Jan 10, 2017 at 1:07 PM, Edmundo Robles
>> wrote:
>>
>>> I have a lot of parse waiting can i kill that process safely
2017-01-10 12:58 GMT-05:00 Edmundo Robles :
> whe i do a ps -fea | grep postgres this is the output
> ostgres 11436 2467 0 11:41 ?00:00:01 postgres: argos_admin vacia
> 127.0.0.1(54880) idle
>
> postgres 19648 2467 0 11:46 ?00:00:00 postgres: argos_admin
> vacia 127.0.0.1(6085
whe i do a ps -fea | grep postgres this is the output
ostgres 11436 2467 0 11:41 ?00:00:01 postgres: argos_admin vacia
127.0.0.1(54880) idle
postgres 19648 2467 0 11:46 ?00:00:00 postgres: argos_admin vacia
127.0.0.1(60858) idle
postgres 19649 2467 0 11:46 ?00:00:00
how can i detect and cancel the process??
--
