From: | Whit Armstrong <armstrong(dot)whit(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: how to cancel a query in progress |
Date: | 2009-06-17 15:56:07 |
Message-ID: | 8ec76080906170856w3dfb9be4u6430c808a78e6d14@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks, Tom.
Lesson learned.
Are there any integrity checks I need to run on the db after this type
of crash and recovery, or is vacuum --all good enough?
-Whit
On Wed, Jun 17, 2009 at 11:19 AM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Whit Armstrong <armstrong(dot)whit(at)gmail(dot)com> writes:
>> I had a few queries that were fired from pgAdmin, but failed to stop
>> running after I killed the GUI.
>
>> I tried to stop the queries by killing the pid (of the process running
>> the query, not the pid of the server) from the linux command line, and
>> much to my surprise, the whole database went down and then recovered
>> (using the data in pg_xlog I assume).
>
> I suppose you used "kill -9"? Don't do that.
>
>> So, now that I've learned this lesson, what is the proper way to kill
>> a query, and can it be done from psql or are there special postgres
>> tools to do this.
>
> kill -INT is a safe query-cancel method.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-06-17 16:06:16 | Re: Playing with set returning functions in SELECT list - behaviour intended? |
Previous Message | Mike Kay | 2009-06-17 15:43:06 | Re: used for large media files |