On Mon, Dec 6, 2010 at 1:46 PM, bricklen <bricklen@xxxxxxxxx> wrote: > On Sat, Dec 4, 2010 at 11:45 AM, felix <crucialfelix@xxxxxxxxx> 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 -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
