From: xiong w. <wan...@gm...> - 2010-12-01 07:50:08
|
Hi, Koichi, core stack: #0 0x00000000007984e2 in MemoryContextStrdup () (gdb) bt #0 0x00000000007984e2 in MemoryContextStrdup () #1 0x00000000005c708b in pgxc_planner () #2 0x00000000006263cb in planner () #3 0x00000000006887e7 in pg_plan_query () #4 0x0000000000688895 in pg_plan_queries () #5 0x000000000054f16b in PrepareQuery () #6 0x0000000000690958 in ProcessUtility () #7 0x000000000068f19b in PortalRunUtility () #8 0x000000000068f310 in PortalRunMulti () #9 0x000000000068e99b in PortalRun () #10 0x0000000000688c76 in exec_simple_query () #11 0x000000000068cbe4 in PostgresMain () #12 0x00000000006555da in BackendRun () #13 0x0000000000654b37 in BackendStartup () #14 0x0000000000651f02 in ServerLoop () #15 0x00000000006516a8 in PostmasterMain () #16 0x00000000005d8f47 in main () Regards, Benny 2010/12/1 Koichi Suzuki <ko...@in...> > Do you have backtrace list of the backend? I hope SEGV may have created > core file. > > Regards; > --- > Koichi Suzuki > > > (2010年12月01日 14:47), xiong wang wrote: > >> Dears, >> template1=# prepare a(int) as insert into t values($1); >> LOG: statement: prepare a(int) as insert into t values($1); >> server closed the connection unexpectedly >> This probably means the server terminated abnormally >> before or while processing the request. >> The connection to the server was lost. Attempting reset: LOG: server >> process (PID 26936) was terminated by signal 11: Segmentation fault >> LOG: terminating any other active server processes >> WARNING: terminating connection because of crash of another server >> process >> DETAIL: The postmaster has commanded this server process to roll back >> the current transaction and exit, because another server process exited >> abnormally and possibly corrupted shared memory. >> HINT: In a moment you should be able to reconnect to the database and >> repeat your command. >> WARNING: terminating connection because of crash of another server >> process >> DETAIL: The postmaster has commanded this server process to roll back >> the current transaction and exit, because another server process exited >> abnormally and possibly corrupted shared memory. >> HINT: In a moment you should be able to reconnect to the database and >> repeat your command. >> Failed. >> Regards, >> Benny >> >> >> >> >> ------------------------------------------------------------------------------ >> Increase Visibility of Your 3D Game App& Earn a Chance To Win $500! >> Tap into the largest installed PC base& get more eyes on your game by >> optimizing for Intel(R) Graphics Technology. Get started today with the >> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. >> http://p.sf.net/sfu/intelisp-dev2dev >> >> >> >> _______________________________________________ >> Postgres-xc-developers mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >> > > |