Re: How to cancel a query if SIGINT does not work?
| От | Tom Lane |
|---|---|
| Тема | Re: How to cancel a query if SIGINT does not work? |
| Дата | |
| Msg-id | 25987.1124471291@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: How to cancel a query if SIGINT does not work? (Adam Witney <awitney@sgul.ac.uk>) |
| Ответы |
Re: How to cancel a query if SIGINT does not work?
Optimize a VIEW question |
| Список | pgsql-general |
Adam Witney <awitney@sgul.ac.uk> writes:
> On 19/8/05 5:27 pm, "Tom Lane" <tgl@sss.pgh.pa.us> wrote:
>> In theory that should always work. What PG version is this? Can you
>> attach to the stuck backend with gdb and get a stack trace?
> Am not particularly familiar with gdb, but if you tell me the steps I will
> do it and report back
Think I've posted this before, but:
Determine PID of backend you are interested in, eg with ps
As postgres user, do
$ gdb /path/to/postgres-executable PID-of-process
gdb prints a bunch of junk
gdb> bt
... copy and paste the output given here ...
gdb> quit
gdb: ok to detach? y
$
If you get a pile of purely numeric output from bt, it's useless
(means you're running symbol-stripped executables). I'm hoping
for at least some function names.
regards, tom lane
В списке pgsql-general по дате отправления: