Re: process exited with status 11 after XLogFlush: request is not satisfied

Hi Tom,

> Hard to tell, though it seems like a good bet. A stack backtrace from
> the core file produced by one of the crashed backends would tell us
> more.

Ok, i have a core file now, running with gdb 5.1.1, this is what comes:

-----------------------snip--------------------------

Core was generated by `postgres: espl espl 213.148.1'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/libcrypt.so.1...(no debugging symbols
found)...done.
Loaded symbols for /lib/libcrypt.so.1
Reading symbols from /lib/libresolv.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/libm.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/ld-linux.so.2
#0 0x08066109 in nocachegetattr ()
(gdb) bt
#0 0x08066109 in nocachegetattr ()
#1 0x080c0bfc in ExecEvalVar ()
#2 0x080c16bb in ExecEvalExpr ()
#3 0x080c179d in ExecEvalExpr ()
#4 0x080c10c8 in ExecEvalFuncArgs ()
#5 0x080c1144 in ExecMakeFunctionResult ()
#6 0x080c1346 in ExecEvalFunc ()
#7 0x080c1740 in ExecEvalExpr ()
#8 0x080c10c8 in ExecEvalFuncArgs ()
#9 0x080c1144 in ExecMakeFunctionResult ()
#10 0x080c1346 in ExecEvalFunc ()
#11 0x080c1740 in ExecEvalExpr ()
#12 0x080c10c8 in ExecEvalFuncArgs ()
#13 0x080c1144 in ExecMakeFunctionResult ()
#14 0x080c12ee in ExecEvalOper ()
#15 0x080c1730 in ExecEvalExpr ()
#16 0x080c1856 in ExecQual ()
#17 0x080c1d26 in ExecScan ()
#18 0x080c742a in ExecSeqScan ()
#19 0x080c03b9 in ExecProcNode ()
#20 0x080c7bba in ExecSort ()
#21 0x080c0449 in ExecProcNode ()
#22 0x080c6406 in ExecMergeJoin ()
#23 0x080c0409 in ExecProcNode ()
#24 0x080bf37d in ExecutePlan ()
#25 0x080bea57 in ExecutorRun ()
#26 0x0810579b in ProcessQuery ()
#27 0x081041c1 in pg_exec_query_string ()
#28 0x08105254 in PostgresMain ()
#29 0x080efe34 in DoBackend ()
#30 0x080ef9ec in BackendStartup ()
#31 0x080eec19 in ServerLoop ()
#32 0x080ee603 in PostmasterMain ()
#33 0x080cebfd in main ()
#34 0x400a2a42 in __libc_start_main () from /lib/libc.so.6

-----------------------snip--------------------------

System: Linux 2.2.17-SMP, PG 7.1.3

Right now the symptomps have changed, we don't get any "status 11" anymore,
but LOTS of

"Server process (pid 2644) exited with status 139 at Wed Jan 30 17:26:50
2002".

When we disable access to db espl, the server runs fine, so I assume a
corrupted record in one of the espl-tables.

Any hints how to find it?

greetings

Bjoern