Skip site navigation (1) Skip section navigation (2)

Re: Update problem on large table

From: Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>
To: bricklen <bricklen(at)gmail(dot)com>
Cc: felix <crucialfelix(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Update problem on large table
Date: 2010-12-06 19:48:47
Message-ID: AANLkTimCJKpQAqmMS21JcZK9hQXK2Cp5g69+3LV-Qqvz@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Mon, Dec 6, 2010 at 1:46 PM, bricklen <bricklen(at)gmail(dot)com> wrote:
> On Sat, Dec 4, 2010 at 11:45 AM, felix <crucialfelix(at)gmail(dot)com> wrote:
>> Ok, I caught one : an update that is stuck in waiting.
>> the first one blocks the second one.
>> ns      |    5902 | nssql   | UPDATE "fastadder_fastadderstatus" SET "built"
>> = false WHERE "fastadder_fastadderstatus"."service_id" = 1
>
> Not sure if anyone replied about killing your query, but you can do it like so:
>
> select pg_cancel_backend(5902);  -- assuming 5902 is the pid of the
> query you want canceled.

How does this differ from just killing the pid?

-- 
Jon

In response to

Responses

pgsql-performance by date

Next:From: Josh KupershmidtDate: 2010-12-06 20:24:31
Subject: Re: Update problem on large table
Previous:From: bricklenDate: 2010-12-06 19:46:04
Subject: Re: Update problem on large table

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group