Re: killing process question - Mailing list pgsql-general

From Tom Lane
Subject Re: killing process question
Date
Msg-id 26819.1032453670@sss.pgh.pa.us
Whole thread Raw
In response to Re: killing process question  ("Johnson, Shaunn" <SJohnson6@bcbsm.com>)
List pgsql-general
"Johnson, Shaunn" <SJohnson6@bcbsm.com> writes:
> --that's just it:  it's not doing a lot of anything.
> --not munching on CPU cycles or anything like that.
> --'ps auwx' shows that the process is stopped
> --(displays a 'T' in the line, i. e.:)

> [snip]
> postgres  3488  5.3  0.0 11412    4 pts/4    T    Sep18  88:53 postgres: joe
> testdb 16.xx.xx.xx SELECT
> [/snip]

Interesting.  Maybe it's waiting for a lock that someone else has?

Can you attach to the process with gdb and get a stack trace to show
where it is, exactly?

    $ gdb /path/to/postgres-executable
    gdb> attach 3488
    gdb> bt
    gdb> quit
    okay to detach? y

            regards, tom lane

pgsql-general by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: Re: [HACKERS] PGXLOG variable worthwhile?
Next
From: Elielson Fontanezi
Date:
Subject: PHP + PostgreSQL