Re: killing process question - Mailing list pgsql-general

From Johnson, Shaunn
Subject Re: killing process question
Date
Msg-id 73309C2FDD95D11192E60008C7B1D5BB04C73F80@snt452.corp.bcbsm.com
Whole thread Raw
In response to killing process question  ("Johnson, Shaunn" <SJohnson6@bcbsm.com>)
Responses Re: killing process question  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general

--sorry, i meant to send this to the group.

--generally speaking, how long should this run?

[snip]

(gdb) attach 3488
Attaching to program: /usr/bin/postgres, process 3488

[/snip]

--i know i should be patient, but i'm trying to figure
--out if this should take more than 20 minutes or if
--i've done something wrong.  (OR, should that be postmaster
--and not postgres in the above line?)

-X

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]

> --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: Frank Joerdens
Date:
Subject: Re: PHP + PostgreSQL
Next
From: Michael Zouroudis
Date:
Subject: cascade problems