From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | ilejn(at)yandex(dot)ru |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Hungry postmaster |
Date: | 2005-06-16 12:46:00 |
Message-ID: | 14550.1118925960@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Ilja Golshtein" <ilejn(at)yandex(dot)ru> writes:
> At the moment on my Linux box I have process
> 'postmaster' eats all CPU. It corresponds
> with connection closed day before -
> not sure if it was normal disconnect.
> strace shows the process constantly
> makes 'send' syscall with EPIPE result.
> Any ideas how to trace this issue
> and/or prevent such thing in the future?
Send it a SIGINT and see if it goes away.
If so, I would bet that someone did an unconstrained join (ie SELECT
the cross product of some large tables) and killed their client instead
of waiting for the result. It's not hard to write a SQL query that will
produce terabytes of output :-(
If SIGINT doesn't kill it pretty quickly, try attaching to it with gdb
so you can get a stack trace.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | rod | 2005-06-16 13:06:19 | Re: pg_dumpall |
Previous Message | Tom Lane | 2005-06-16 12:35:49 | Re: [HACKERS] INHERITS and planning |