| From: | Kenneth Marshall <ktm(at)rice(dot)edu> |
|---|---|
| To: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
| Cc: | Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>, bricklen <bricklen(at)gmail(dot)com>, felix <crucialfelix(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Update problem on large table |
| Date: | 2010-12-06 20:26:56 |
| Message-ID: | 20101206202656.GK19162@aart.is.rice.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Dec 06, 2010 at 03:24:31PM -0500, Josh Kupershmidt wrote:
> On Mon, Dec 6, 2010 at 2:48 PM, Jon Nelson <jnelson+pgsql(at)jamponi(dot)net> wrote:
> > On Mon, Dec 6, 2010 at 1:46 PM, bricklen <bricklen(at)gmail(dot)com> wrote:
> >> 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?
>
> pg_cancel_backend(5902) does the same thing as:
> kill -SIGINT 5902
>
> Josh
>
Yes, but you can use it from within the database. The kill command
requires shell access to the backend.
Cheers,
Ken
| From | Date | Subject | |
|---|---|---|---|
| Next Message | felix | 2010-12-06 21:31:44 | Re: Update problem on large table |
| Previous Message | Josh Kupershmidt | 2010-12-06 20:24:31 | Re: Update problem on large table |