Re: "pgbench -c 13" causes backend hangup.
От | Yutaka tanida |
---|---|
Тема | Re: "pgbench -c 13" causes backend hangup. |
Дата | |
Msg-id | 20010916150456.2D6B.YUTAKA@hi-net.zaq.ne.jp обсуждение исходный текст |
Ответ на | Re: "pgbench -c 13" causes backend hangup. (Jason Tishler <jason@tishler.net>) |
Ответы |
Re: "pgbench -c 13" causes backend hangup.
|
Список | pgsql-cygwin |
Jason, On Sat, 15 Sep 2001 10:29:32 -0400 Jason Tishler <jason@tishler.net> wrote: > Can you attach to the hung postgres.exe processes and get a backtrace to > determine where they are hanging? Here's log, but it's nothing to use....So,I can't determine what's wrong. -- bash-2.05$ gdb -nw GNU gdb 5.0 (20010428-1) (snip) (gdb) attach 776 Attaching to process 776 [Switching to thread 776.0x5b0] (gdb) backtrace #0 0x77fa018d in ?? () #1 0x77e5758a in ?? () -- There's a backend log when they're hanged. -- DEBUG: ProcessUtility: end DEBUG: CommitTransactionCommand DEBUG: proc_exit(0) DEBUG: shmem_exit(0) DEBUG: exit(0) postmaster: reaping dead processes... postmaster: CleanupProc: pid 1480 exited with status 0 -- I suppose it's a bug of cygwin's signal handling.I'll trying to create other testcase. --- Yutaka tanida<yutaka@hi-net.zaq.ne.jp> 謎のWebsite http://www.hi-net.zaq.ne.jp/yutaka/
В списке pgsql-cygwin по дате отправления: