Re: Unsuccessful SIGINT - More Info
От | Brian Wipf |
---|---|
Тема | Re: Unsuccessful SIGINT - More Info |
Дата | |
Msg-id | CBBACA86-F20C-49BC-A352-E6C186EC4326@clickspace.com обсуждение исходный текст |
Ответ на | Re: Unsuccessful SIGINT - More Info (Martijn van Oosterhout <kleptog@svana.org>) |
Список | pgsql-general |
On 2-Dec-06, at 6:27 AM, Martijn van Oosterhout wrote: > On Fri, Dec 01, 2006 at 08:26:53PM -0700, Brian Wipf wrote: >> Now I know the cause at least. If anyone has an idea on how to kill a >> similar hung connection without rebooting the server, I would >> appreciate any suggestions. > > I'm unsure about why it wouldn't respond to a sigint, but did you try > try stronger signals? I tried a SIGHUP, SIGINT and SIGQUIT. Do you believe a postgres process in the following: #0 0x00002ba62c18f085 in send () from /lib64/libc.so.6 #1 0x0000000000504765 in internal_flush () #2 0x0000000000504896 in internal_putbytes () #3 0x00000000005048fc in pq_putmessage () #4 0x0000000000505ea4 in pq_endmessage () ... is listening for some other signal? I, of course, didn't try a SIGKILL. This is a production database. Brian Wipf <brian@clickspace.com>
В списке pgsql-general по дате отправления: