| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Wei Weng <wweng(at)kencast(dot)com> |
| Cc: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Resources |
| Date: | 2002-01-10 22:09:40 |
| Message-ID: | 23072.1010700580@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Wei Weng <wweng(at)kencast(dot)com> writes:
> I have a side question. How do I stop this kind of crazy query to suck up
> my CPU power if it is fed by a database driver? (like ODBC, for example)
> Since kill -9 postmaster is highly not recommended, can i do a
> /sbin/service postgresql stop to force it to shut down?
That would shut down the whole database, which is likely not what you
want. The best way to cancel a runaway query is to cancel it, ie,
send a cancel request from the client (cf. control-C in psql, dunno
whether the ODBC driver supports this). If you are logged into the
postgres or root account on the DB machine, you can get the same
effect with "kill -INT pid-of-backend". (not pid-of-postmaster)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter T. Brown | 2002-01-10 22:27:07 | replication |
| Previous Message | SHELTON,MICHAEL (Non-HP-Boise,ex1) | 2002-01-10 21:59:08 | Re: Resources |