Re: "pgbench -c 13" causes backend hangup. - Mailing list pgsql-cygwin
From | Yutaka tanida |
---|---|
Subject | Re: "pgbench -c 13" causes backend hangup. |
Date | |
Msg-id | 20010916235515.E085.YUTAKA@hi-net.zaq.ne.jp Whole thread Raw |
In response to | Re: "pgbench -c 13" causes backend hangup. (Jason Tishler <jason@tishler.net>) |
Responses |
Re: "pgbench -c 13" causes backend hangup.
(Jason Tishler <jason@tishler.net>)
|
List | pgsql-cygwin |
Jason, On Sun, 16 Sep 2001 10:34:50 -0400 Jason Tishler <jason@tishler.net> wrote: > I believe that you need to start gdb as follows: (snip) Thanks for your information . I can get a backtrace log. -- (gdb) bt #0 0x77f827e8 in _libkernel32_a_iname () #1 0x77e56a15 in _libkernel32_a_iname () #2 0x77e56a3d in _libkernel32_a_iname () #3 0x00538a5d in semop () #4 0x004cf450 in IpcSemaphoreLock (semId=5250, sem=11, interruptOK=1 '\001') at ipc.c:426 #5 0x004d48b9 in ProcSleep (lockMethodTable=0xa0102e8, lockmode=4, lock=0x1abf527c, holder=0x1abf770c) at proc.c:666 #6 0x004d3795 in WaitOnLock (lockmethod=1, lockmode=4, lock=0x1abf527c, holder=0x1abf770c) at lock.c:955 #7 0x004d351c in LockAcquire (lockmethod=1, locktag=0x22f338, xid=3288, lockmode=4) at lock.c:739 #8 0x004d2b11 in XactLockTableWait (xid=3280) at lmgr.c:310 #9 0x0040c61b in heap_update (relation=0xa07e5a0, otid=0x22f488, newtup=0xa0ae810, ctid=0x22f408) at heapam.c:1627 #10 0x0048517a in ExecReplace (slot=0xa0ae010, tupleid=0x22f488, estate=0xa0ade50) at execMain.c:1451 #11 0x00484dc1 in ExecutePlan (estate=0xa0ade50, plan=0xa0addb0, operation=CMD_UPDATE, numberTuples=0, direction=ForwardScanDirection, destfunc=0xa0ae650) at execMain.c:1125 #12 0x00483f2a in ExecutorRun (queryDesc=0xa0ade38, estate=0xa0ade50, feature=3, count=0) at execMain.c:233 #13 0x004db703 in ProcessQuery (parsetree=0xa0ab000, plan=0xa0addb0, dest=Remote) at pquery.c:295 #14 0x004d8ff9 in pg_exec_query_string ( query_string=0xa0aaca8 "update tellers set tbalance = tbalance + 850 where t id = 2\n", dest=Remote, parse_context=0xa025318) at postgres.c:810 #15 0x004daf29 in PostgresMain (argc=4, argv=0x22f778, real_argc=2, real_argv=0x614e2414, username=0xa01cc29 "Administrator") at postgres.c:1908 #16 0x004bfaf2 in DoBackend (port=0xa01c9c0) at postmaster.c:2114 #17 0x004bf662 in BackendStartup (port=0xa01c9c0) at postmaster.c:1897 #18 0x004be18d in ServerLoop () at postmaster.c:995 #19 0x004bd54c in PostmasterMain (argc=2, argv=0x614e2414) at postmaster.c:685 #20 0x00497551 in main (argc=2, argv=0x614e2414) at main.c:171 #21 0x6100401e in _libkernel32_a_iname () #22 0x6100421d in _libkernel32_a_iname () #23 0x6100425c in _libkernel32_a_iname () #24 0x0053924b in cygwin_crt0 () at /cygnus/netrel/src/cygwin-1.3.3-2/winsup/cygwin/lib/cygwin_crt0.c:33 -- Hmm... , it it a cygipc probrem? --- Yutaka tanida<yutaka@hi-net.zaq.ne.jp> 謎のWebsite http://www.hi-net.zaq.ne.jp/yutaka/
pgsql-cygwin by date: